Skip to content

Import user context without a Configure account ​

Invite-only

Configure enables this flow for approved partners. A secret key alone does not grant access. Keys without partner access receive 404 from these endpoints. Contact Configure to enable the flow.

This flow imports context from the user's existing assistants into your app. It does not require a Configure account or phone verification.

You keep your own user ID. Configure never sees an email or a phone number, and you read the finished profile back with the same ID you already use.

What the user sees ​

The hosted flow displays your app's name and these steps:

  1. A list of the assistants you asked for, each with an Import button.
  2. Tapping one opens that assistant with the export request already written (ChatGPT and Claude). Gemini and Grok cannot take a prompt from a link, so for them it copies the request to the clipboard.
  3. The user pastes the export into Configure. The page validates the content.
  4. A confirmation screen displays the result and a button to return to your app.

1. Create a session when the user clicks ​

Create the session on your server with your secret key when the user selects the connection button. The URL expires after 15 minutes.

The request and response examples below assume an installation whose default is import_only, with connect disabled. If your installation enables connect, include "flow": "import_only" in the request to select this flow explicitly. Omitting it selects the installation default and can require phone verification.

bash
curl -X POST https://api.configure.dev/v1/flows/sessions \
  -H "X-API-Key: $CONFIGURE_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "partner_ref": "your-own-user-id",
    "sources": ["chatgpt", "claude"],
    "return_url": "https://yourapp.example/welcome"
  }'
FieldRequiredNotes
partner_refyesYour opaque ID for this user. Up to 200 characters of letters, digits and . _ : @ - . Not an email or a phone number, and it is rejected if it looks like one.
flownoLeave it out to get your installation's default: the connect flow (the import screen, then the phone and the code, then a Configure account bound to your user ID) wherever your installation has it, which every installation made since Sep 29 2026 does. An installation without it gets the import-only flow. Send "import_only" to always get the import-only page with no phone step.
sourcesnoAny of chatgpt, claude, gemini, grok. Defaults to all four. The page shows exactly what you ask for and nothing else.
return_urlnoWhere the confirmation screen sends the user. Must be https on a host registered on your developer account.
json
{
  "id": "d98ef4a7-4d7d-41a8-b4a5-8b818b20cd54",
  "status": "created",
  "livemode": true,
  "partner_ref": "your-own-user-id",
  "sources": ["chatgpt", "claude"],
  "imports": [],
  "return_url": "https://yourapp.example/welcome",
  "profile_ready": false,
  "failure": null,
  "expires_at": "2026-09-14T06:08:19.690Z",
  "url": "https://accounts.configure.dev/f/cfgfh_rEfo5Fac..."
}

Send the user to url. Nothing else from this response belongs in a browser.

Do not create links in advance

expires_at is 15 minutes out, and the link is single use. Do not create links ahead of time. They expire unused.

Checking your branding without a browser ​

The hosted page renders its branding in the browser. A raw HTML request does not show the final app name. The JavaScript fallback 'This app' does not indicate a branding error.

To verify branding through the API, extract the cfgfh_... token from the returned url:

bash
curl "https://api.configure.dev/v1/flows/handoff/$HANDOFF" \
  -H "Origin: https://accounts.configure.dev" \
  -H "X-Configure-Client: hosted-flow"

agent_display_name in the response is exactly what the headline will read. If it comes back null, the agent record is misconfigured and only Configure can fix it.

2. The user does the import ​

The hosted flow opens the assistant, provides the export request, validates pasted content, handles retries, and displays the confirmation screen.

partner_ref never reaches the browser. The URL carries a 256 bit handoff token. That token is exchanged once, on an explicit gesture, for a __Host- cookie scoped to that one session. The handoff token cannot be reused after this exchange.

3. Read the result ​

The callback can occur after completion or abandonment. Read the session status from the API to determine the result.

bash
curl https://api.configure.dev/v1/flows/sessions/$SESSION_ID \
  -H "X-API-Key: $CONFIGURE_SECRET_KEY"
json
{
  "id": "d98ef4a7-4d7d-41a8-b4a5-8b818b20cd54",
  "status": "ready",
  "imports": [
    { "source": "chatgpt", "status": "completed", "memory_count": 5 }
  ],
  "profile_ready": true,
  "failure": null
}
statusMeaning
createdCreated, not opened yet.
openedThe user is on the page.
importingAt least one paste is being processed.
readyEvery import finished.
failedThe import could not be processed. failure.code says why and failure.retryable says whether a fresh link would help.
expiredNobody opened it in time. Set lazily, when the session is next read. A session past expires_at reports expired on your next poll, not at the moment it lapsed.
abandonedThe user opened the page and left before every import finished. Set lazily too, on the first read past expires_at.

A user who opens the page and leaves stays opened until the session lapses, then reads back as abandoned. The link opens on the user's first tap, not on page load. A user who loads the page and leaves without tapping reads back as expired.

4. Read the profile with your own ID ​

Send the same ID you sent as partner_ref, in the X-User-Id header. Use the standard profile endpoint with your existing credentials.

bash
curl https://api.configure.dev/v1/profile \
  -H "X-API-Key: $CONFIGURE_SECRET_KEY" \
  -H "X-User-Id: your-own-user-id"
json
{
  "linked": false,
  "identity": { "interests": ["Rust", "site reliability"] },
  "summary": "Rae is a principal SRE in Oslo who wants the runbook step first...",
  "imports": {
    "chatgpt": { "memory_count": 5, "importedAt": "2026-09-14T05:43:16.043Z" }
  }
}

Summary generation follows import completion

ready indicates that all imports completed. Summary generation runs afterward and has taken about 10 seconds in end-to-end tests. An immediate profile read can return memories with an empty summary. If the summary is empty, read it again after a short delay.

Test mode ​

Use your sk_test_ key. Test sessions resolve against your test developer account and can never touch a live user. Everything else behaves the same.

What can go wrong ​

The user seesWhyWhat you do
This link has expiredMore than 15 minutes passedCreate a new one on the next click.
This link was already usedOpened in a different browserCreate a new one.
That is the request itselfThey pasted the prompt, not the answerNothing. The page says so and waits.
That does not look like an exportThe paste is too short and unformatted to be an export. A refusal like "I'm sorry, I can't help with that" looks like thisNothing. The page says so and waits. A messy but substantial reply is still accepted and normalised.
Nothing to import in that exportThe assistant returned an empty exportNothing. They can try another source.

What this flow does not do ​

It does not ask for, receive or store an email address or a phone number. The profile stays keyed to your partner_ref. If the same person uses two of your products, they get two profiles unless you send the same partner_ref for both.

If you need a linked Configure account bound to your user ID, use the linked-account flow. You need it for MCP connect links, or to share approved context with agents in other products. It uses the same key and the same session endpoints, with a phone step before the imports.

Infrastructure to connect agents, apps, and chats