Skip to main content

Connect via API

Use the public API to list capture catalogs and read catalog details from your own application. Choose gRPC for generated clients (including gRPC-Web for browsers), or REST for JSON over HTTP.

Before you start​

  1. Sign in to the Reconstruct Platform, open Settings → API tokens, and create a token with the Platform API scope (api). Copy the secret when it appears; it is shown only once.
  2. Set CR_RECONSTRUCT_API_TOKEN in the environment that runs your server-side client. Tokens with only the MCP scope do not authenticate PlatformService.
  3. Use https://reconstruct.dev/api/v1/platform for REST and https://reconstruct.dev for gRPC-Web. Native gRPC clients connect to reconstruct.dev:443 over TLS.

Pass the token as Authorization: Bearer <token> on every request.

Choose an API style​

StylePublic endpointGuides
gRPCreconstruct.dev:443 for native gRPC; https://reconstruct.dev for gRPC-WebOverview and client generation
RESThttps://reconstruct.dev/api/v1/platformEndpoints and examples

Both styles expose catalog listing, version details, insights, stored files and exports, plus the caller’s requests. Use the returned nextPageToken (REST) or next_page_token (gRPC) to request the next page. Get catalog IDs from the list response.

Use CreateRequest, ListRequests and GetRequest to submit a product and track your own requests. Requests are reviewed before capture. The response shows the decision, safety status and capture progress.