Worker Code

​

Template or code

• Template (default): the Worker is generated from the template. Saving creates a preview on its own URL; Deploy to production in the bar on the Worker tab serves it to your consumers. View generated code shows exactly what runs.
• Code: Edit code stores the generated files as yours. From then on nothing is regenerated. Deploy preview puts your files on their own URL; Deploy to production (in the editor, the bar or Promote on the Deployments tab) serves them to your consumers. Back to template deletes them and generates the Worker again, as a preview too.
• From the CLI or GitHub: deploying files with jojapi deploy (or from GitHub) to an API in template mode switches it to code mode. The files become a preview deployment; production keeps serving the template’s deployment until you promote them (jojapi deploy --prod does both at once). Back to template restores the template.

​

Files

index.mjs            required: export default { fetch }
endpoints/*.mjs      a handler per endpoint, if you like that layout
lib/**/*.mjs         your modules, imported with relative paths
*.json, *.txt        JSON and text modules

// index.mjs
import { search } from "./endpoints/search.mjs";

export default {
  async fetch(request, env, ctx) {
    switch (request.headers.get("x-jojapi-endpoint")) {
      case "GET /search":
        return search(request, env);
      default:
        return new Response(JSON.stringify({ message: "Not found" }), { status: 404, headers: { "content-type": "application/json" } });
    }
  },
};

​

The contract with the gateway

​

Request headers your Worker receives

​

Response headers your Worker may set

​

Billing

​

Variables

​

Storage and queues

​

Console logging and limits

• Console logging (Worker tab → Errors & logs): captures what your Worker writes with console.* and the stack of uncaught exceptions. It is separate from the request log, which records every request anyway. It stays on until you switch it off, and each request then costs a little more to process: the cost appears under Compute usage as Console logging (per invocation) and Console log lines (per stored line). The last 500 lines are kept.
• Limits: a request may use up to 30 seconds of CPU time and 50 outgoing requests, with an upstream call of at most 90 seconds. The platform raises these per API when an API needs more; write to support.

​

Compute usage

​

Runtime errors

​

Proxies and the egress relay

​

Browser impersonation

const res = await fetch("https://www.example.com/", {
  headers: {
    "x-jojapi-relay-impersonate": "chrome",
    "x-jojapi-relay-proxy": env.PROXY_URL, // optional
  },
});

• Profiles: chrome, chrome_android, edge, firefox, safari and safari_ios follow the newest version the platform has, or pin one such as chrome146, firefox144 or safari184. An unknown profile answers 400.
• Headers: yours replace the profile’s same-named ones in place, so set your own user-agent, cookies or accept-language when you need them. The profile keeps accept-encoding, and the body reaches your Worker already decoded.
• The response carries x-jojapi-relay-impersonate with the exact profile used.
• Without the header, requests keep the default client (HTTP/1.1).
• Failures of your own proxy are named in the relay’s 502 answer, for example Proxy Tunnel Refused (407).

​

Local development

curl http://127.0.0.1:8787/users/42 \
  -H 'x-jojapi-endpoint: GET /users/{id}' \
  -H 'x-jojapi-params: {"id":"42"}' \
  -H 'x-jojapi-user-nick: alice' -H 'x-jojapi-plan-type: periodic'