AI + No-code Guide

Use FakeAPI as a backend-shaped fake API for builders, bots, and no-code platforms.

The core purpose of FakeAPI is to act as a reliable fake backend listener for no-code tools, agentic workflows, prototypes, frontend teams, and implementation planning. Chatbots and no-code systems should treat it like a programmable listener that echoes the fakeresponse they send.

Simple authNamespace + token

Stable runtimeUse namespace routes like /client-demo/auth/login

Agent-friendlyLog every request and inspect it from the dashboard

1. How a chatbot should register

If the user does not already have a namespace and token, the chatbot should first reserve a namespace. If the namespace is free, FakeAPI returns a one-time token. The chatbot must tell the user to store that token safely.

Step 1: Reserve a namespace POST https://fakeapi.vexlo.ca/api/auth/reserve Content-Type: application/json { "namespace": "client-demo" } Save the token immediately. It is shown only once.

2. How a chatbot should log in later

For all future management actions, the chatbot should use the saved namespace and token. This verifies access before creating, updating, or deleting endpoints.

3. How to drive an inline fake response

A chatbot or no-code flow should send the request it wants to test directly to the namespace route, and include a top-level fakeresponse. This is ideal for demos, QA, and frontend integration because the server does not need a stored endpoint definition first.

Step 3: Send a request with fakeresponse POST https://fakeapi.vexlo.ca/client-demo/auth/login Content-Type: application/json { "email": "[email protected]", "password": "secret", "fakeresponse": { "statusCode": 200, "headers": { "content-type": "application/json" }, "body": { "result": true, "message": "login successful" } } }

Put the exact response you want inside fakeresponse.
If fakeresponse is missing, FakeAPI returns a validation-style error that shows the expected shape.
Use the dashboard as a log viewer, not as a service builder.

4. How to delete an endpoint

To remove an endpoint, first fetch the dashboard or endpoint list, identify the endpoint id, then call the delete API with the same namespace and bearer token.

Step 4: Delete an endpoint DELETE https://fakeapi.vexlo.ca/api/console/namespaces/client-demo/endpoints/ENDPOINT_ID Authorization: Bearer

5. How to export all endpoints for AI

This is the main integration point for agents. It returns the namespace metadata, endpoint inventory, inline responses, and record flow hints so a chatbot can understand the whole fake backend in one request.

Step 5: Export for AI or no-code sync POST https://fakeapi.vexlo.ca/api/ai/export Content-Type: application/json { "namespace": "client-demo", "token": "paste-the-saved-token" }

How no-code platforms should use FakeAPI

Use FakeAPI as the temporary backend for forms, dashboards, onboarding flows, and internal tools.
Map UI actions to versioned fake endpoints مثل /client-demo/v1/users or /client-demo/v1/auth/login.
Keep contract design in FakeAPI first, then switch the no-code frontend to the real backend later.
Use the AI export endpoint to give builders or agents a full picture of the current fake backend.