> ## Documentation Index > Fetch the complete documentation index at: https://docs.purps.lol/llms.txt > Use this file to discover all available pages before exploring further. # Submit the signed change > Step 2: the same body as prepare, plus `ts`, `nonce` and the wallet's `signature` over the message prepare returned (ed25519 over the UTF-8 bytes, base58). The signer must be the wallet named in prepare: the coin's owner, which is whoever holds its creator rewards, or a platform admin wallet (admins act and change strategy; only the owner can ask for authority or hand the coin on). The nonce only fits the wallet, coin and exact action it was issued for and lives five minutes; a signature is good once. A malformed body is a 400 that names the field, before any signature is looked at. Every money check runs here on the server's own figures, so a change the coin page would refuse is refused here too. An `action` is queued for the engine and answers `queued` with the command id; watch /coins/{mint}/changes for done or failed, and /coins/{mint} for the position. A `strategy` change is applied at once and answers `changed`, the lines that differ. A `request` answers the request's `id` and `status`. A `handover` answers the new `payoutWallet`. Refusals: 401 for a bad signature, a nonce not issued for this wallet and action, or a timestamp older than five minutes; 403 when authority is not on for the coin; 409 when the coin is not live, the market already has an action running, nothing changed, or the signature was already used; 422 when a money check refuses it, with the reason; 423 frozen; 429 for the per-day action count or a cooldown still running; the reason says how long. ## OpenAPI ````yaml /openapi.json post /coins/{mint}/authority/submit openapi: 3.1.0 info: title: PURPS API version: 2.0.0 description: >- Everything purps.lol can do, as JSON. Read the coin list, a coin's full page and the launchpad; launch coins on purps.lol, pump.fun and Pons; wire an existing pump.fun coin's fees into a strategy; steer a coin you own. No key, no signup. A launch is one call that returns unsigned transactions: the launch transaction can only land with your wallet's signature, and that is the proof. The few writes that need a message signature (Pons launches, wiring a strategy onto a coin, creator authority) come as a prepare/submit pair. Every transaction is signed in your wallet, never by us. Every response is `{ ok: true, data }` or `{ ok: false, error }`. Cross-origin requests are allowed from any site. Every answer from the API itself carries `RateLimit-Limit` and `RateLimit-Policy`; uncached ones (writes, prepare and submit, refusals) carry `RateLimit-Remaining` and `RateLimit-Reset` as well. The 503 while the API is paused and the 410 on old v1 write addresses carry neither. servers: - url: https://purps.lol/api/v2 security: [] tags: - name: Coins description: Read what the site shows. - name: Launch on purps.lol description: Launch a coin on purps.lol. Build, sign, send, poll. - name: Launch on pump.fun description: Launch straight on pump.fun with fees wired to a strategy. - name: Launch on Pons description: Launch through Pons, the launchpad on Robinhood Chain. - name: Redirect a pump.fun coin description: Point an existing pump.fun coin's creator fees at a strategy. - name: Manage a coin description: Attach a strategy to a coin launched without one. Creator-signed. - name: Creator authority description: >- Steer a purps.lol coin you own: act on a position, change its strategy, ask for authority, or hand the coin on. Every move is signed by the owner's wallet and published on the coin's Changes tab. - name: Transactions description: Send a signed Solana transaction through our relay and watch it land. paths: /coins/{mint}/authority/submit: post: tags: - Creator authority summary: Submit the signed change description: >- Step 2: the same body as prepare, plus `ts`, `nonce` and the wallet's `signature` over the message prepare returned (ed25519 over the UTF-8 bytes, base58). The signer must be the wallet named in prepare: the coin's owner, which is whoever holds its creator rewards, or a platform admin wallet (admins act and change strategy; only the owner can ask for authority or hand the coin on). The nonce only fits the wallet, coin and exact action it was issued for and lives five minutes; a signature is good once. A malformed body is a 400 that names the field, before any signature is looked at. Every money check runs here on the server's own figures, so a change the coin page would refuse is refused here too. An `action` is queued for the engine and answers `queued` with the command id; watch /coins/{mint}/changes for done or failed, and /coins/{mint} for the position. A `strategy` change is applied at once and answers `changed`, the lines that differ. A `request` answers the request's `id` and `status`. A `handover` answers the new `payoutWallet`. Refusals: 401 for a bad signature, a nonce not issued for this wallet and action, or a timestamp older than five minutes; 403 when authority is not on for the coin; 409 when the coin is not live, the market already has an action running, nothing changed, or the signature was already used; 422 when a money check refuses it, with the reason; 423 frozen; 429 for the per-day action count or a cooldown still running; the reason says how long. operationId: submitAuthority parameters: - name: mint in: path required: true description: >- The token's mint address (Solana) or contract address (Robinhood Chain). schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/AuthoritySubmit' responses: '200': description: Queued, applied, requested or handed over. content: application/json: schema: type: object properties: ok: type: boolean enum: - true data: $ref: '#/components/schemas/AuthorityResult' '400': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '423': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Every failure carries the same envelope. content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: AuthoritySubmit: type: object description: 'Everything in AuthorityPrepare, plus:' properties: ts: type: integer description: The `ts` prepare returned. required: true nonce: type: string description: The `nonce` prepare returned. required: true signature: type: string description: The wallet's ed25519 signature over `message`, base58. required: true AuthorityResult: type: object properties: kind: type: string description: As sent. enum: - action - strategy - request - handover mint: type: string description: The coin. url: type: string description: Its page. queued: type: string description: >- `action`: the id of the command queued for the engine. Watch /coins/{mint}/changes for done or failed. nullable: true changed: type: array description: >- `strategy`: the lines that differ from before, as the Changes tab shows them. items: type: string nullable: true id: type: string description: '`request`: the request''s id.' nullable: true status: type: string description: '`request`: the request''s status, `pending` until reviewed.' nullable: true payoutWallet: type: string description: >- `handover`: the wallet that now holds the rewards. Null when handed back to the launching wallet. nullable: true Error: type: object properties: ok: type: boolean description: Always false on a failure. error: type: string description: >- A short reason in plain words: `coin not found`, `too many requests`, `invalid wallet signature`. ````