# Mint connect link > Markdown version of https://docs.postlake.dev/api/post-connect-link . The canonical page for humans. > PostLake is the social media API for AI agents: https://postlake.dev/llms.txt `POST /v1/connect-link` Mint a short-lived link to the hosted connect/manage page ## Request Authenticate with a bearer API key. Agents calling over MCP authorise with OAuth instead and never handle the key. ```bash curl -X POST https://api.postlake.dev/v1/connect-link \ -H "Authorization: Bearer $POSTLAKE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"profile":"…"}' ``` ### Body | Field | Type | Required | What it is | | --- | --- | --- | --- | | `profile` | string | No | | ## Response Success (`200`). | Field | Type | Required | What it is | | --- | --- | --- | --- | | `url` | string | Yes | | | `expiresInSeconds` | integer | Yes | | ### Example ```json { "url": "…", "expiresInSeconds": 0 } ``` ## Calling this from an agent Agents working over the hosted MCP server reach the same product through tools rather than REST, and authorise with OAuth so your API key is never pasted into a chat. ## Errors Every failure uses one shape: a stable `type`, a granular `code`, the field at fault in `param`, and a plain-language `fix`. See https://docs.postlake.dev/errors.md . Retries are safe: send the same `Idempotency-Key` and a call that already succeeded returns its original result rather than repeating it. ## Common questions **Is it safe to retry this call?** Yes. Send the same Idempotency-Key and a call that already succeeded returns its original result instead of repeating the work. That is what makes it safe to hand to an agent that retries on its own. **What happens when it fails?** You get one error shape: a stable type, a granular code you can branch on, the offending field in param, and a fix written so an agent can correct itself rather than stop. Full list on Errors and retries. ## Related - [Mint app link](https://docs.postlake.dev/api/post-app-link.md) `POST /v1/app-link`