jojapi CLI works with your APIs from a terminal, a CI job or an AI agent. It uses the Management API with a scoped token. Every write that cannot be undone shows what will change and asks before it runs.
jojapi pull, commands use the API named in jojapi.json unless you pass a slug.
Token scopes
Give the token the scopes your commands use. A command whose scope is missing stops and names the scope it needs.Code and deployments
--prod on deploy, resources, vars or mode puts only that change into production at once, for example to rotate a leaked key. jojapi deployments keep|public|archive <id> changes one deployment, and jojapi changes discard returns the working copy to what production runs. To deploy from GitHub, see Deploy from GitHub.
Bindings, variables and settings
resources remove and vars unset ask before they run. Removed storage and its data are deleted once no active deployment uses it, so a rollback still finds it. See Shared resources for grants between APIs.
Endpoints as code
jojapi export writes the API as an OpenAPI 3.2 document, hidden endpoints included. Importing that document again changes nothing, so you can keep it in a repository and edit it there:
jojapi import changes nothing until you add --apply. First it prints every change, field by field:
- new endpoints, with their parameters, body and responses;
- for changed endpoints, each value before and after, with JSON paths inside schemas and examples;
- endpoints missing from the document;
- the API’s details.
--apply --expect <digest> applies that preview and nothing else. If the document, the options or the API changed since the preview, it refuses. Without a terminal, which covers CI and agents, --apply requires --expect. In a terminal, --apply without --expect shows the preview and asks first.
What an import changes, and what it leaves alone:
The CLI reads OpenAPI (JSON or YAML) and Postman Collections, from a file or a URL.
jojapi import without a source re-imports from the URL of the last import. RapidAPI and Apify imports run in the Studio.
For quick edits there are smaller commands. jojapi endpoints show|add|update|hide|disable|delete|duplicate|move changes one endpoint, and jojapi endpoints example stores a response example. jojapi groups, jojapi faqs and jojapi objects manage the rest of the listing. jojapi update --marketplace public submits the API for review, and if it is refused it names the checks that failed. jojapi page shows the marketplace page as consumers see it.
Pricing
plans add-object will email, and the fact that a grant adds again if you run it twice. See Billable objects and Agent payments.
Traffic and logs
--json; a jk_ key is shortened to its last four characters. Request bodies are never logged. --details adds the consumer’s IP address, the headers and the response body.
Scripts and agents
- Read commands,
deploy,import,resources,varsandmodetake--jsonand print one line of JSON. Progress goes to stderr. - A command that asks first won’t run without a terminal; it prints what would change instead.
--yesanswers the question.import --applytakes--expect <digest>instead of--yes. - Exit code
0means done, or nothing to do. Any other code means a refusal, a failure or a usage error, with the reason on stderr. JOJAPI_TOKENandJOJAPI_BASEoverride the stored configuration, so CI needs onlyJOJAPI_TOKEN.