Skip to main content

Connect to an Existing Backend

Dependencies

Build a New App With Payments or Add Payments to an Existing App - the builder must be run first so that you can choose how to handle the backend.

Example prompts

"Connect this app to the backend running at http://localhost:8000", "App uses a backend with specs @openapi.json."

You give the builder the base URL. Before wiring anything, it verifies the service is configured correctly by reading the service's own API description - the OpenAPI or Swagger document most frameworks publish automatically. It sends only GET requests to documentation URLs, so it can never accidentally open an order against your live service.

The builder then reports one of four results:

  • Endpoint found - The backend includes the endpoint the app needs. The builder asks whether you want to connect the app to it.
  • No endpoint - The backend is available, but it does not include the required endpoint. The builder offers you a sample backend instead.
  • No description - The backend is available, but the builder cannot find a document describing it, so the endpoint cannot be verified. You can provide the document or specify the endpoint path manually. If you provide only the path, the builder continues but informs you that it was not verified.
  • Unreachable - The builder cannot connect to the backend. It asks whether the backend is temporarily not running. If you confirm that it exists, the builder continues with the implementation.

If the endpoint is missing or returns information in the wrong format, the builder explains the problem before connecting the app. The app can still be built and launched, but real payments will not work until the required endpoint is available. The builder clearly informs you about this in the result.