login, so there’s nothing else to set up. Pass the HTTP method and the path, and the command returns the server’s response. Find the path with api search or api catalog.
Paths from the spec contain placeholders in braces, such as {app_id} and {workflow_id}. The command fills in {app_id} from --app-id, the BASE44_APP_ID environment variable, or the linked project. Replace any other placeholder with a real value before you send the request.
The command doesn’t check the request before sending it. If something’s wrong, you get the server’s error message and a request ID. When you’ve hit a rate limit, the error also says how long to wait before trying again.
The command doesn’t time out, so a slow operation such as a deploy still returns its response, even if it takes minutes.
To see what an operation expects before you call it, add --help after the method and path. The command prints the operation’s contract as JSON, with its parameters, request body schema, and response schema, and sends nothing.
Usage
Arguments
Flags
Example
Check what an operation expects, then call it:workspaceId query parameter, which the command doesn’t fill in for you. Run workspace list to find it:
Output
The command returns the response body as the server sent it. In a terminal, JSON is formatted so it’s easier to read. When you pipe the output to another program, it’s passed through unchanged, so large numbers aren’t rounded. When the body is empty, binary, or saved to a file, the command returns a short JSON summary instead of the body:See also
api grep: Search the API spec with a regular expressionexec: Run a script with the Base44 SDK pre-authenticated- Base44 APIs: The REST APIs and their references