Sign-ins and passkeys

List passkeys

Returns every registered owner passkey, oldest first. Requires the owner's browser session or sign_ins.manage.

GET
/owner/passkeys

Authorization

cookie__Host-marfa_session<token>

The owner's browser sign-in, which only the sign-in pages read: here, the passkey doors. On plain HTTP on this machine, the cookie is marfa_session. Writes require this instance's Origin, and changes require authentication within fifteen minutes. Apps cannot use this authority.

Response body

About errors

Returns every registered owner passkey.

application/json
  1. response

Every registered owner passkey.

data*array<>

Every registered owner passkey, oldest first.

next_cursor*null

Always null: every passkey is returned in one page.

  • validation_error: the query has a parameter this endpoint doesn't take.
application/json
  1. response

An error response.

error*

What went wrong.

unauthorized: the request has no credential, or its credential is not valid. For a key that has expired, details.expired_at says when it expired.

application/json
  1. response

An error response.

error*

What went wrong.

  • forbidden: the credential lacks sign_ins.manage. details.required_scope names it.
application/json
  1. response

An error response.

error*

What went wrong.

contract_mismatch: X-Marfa-Contract names another contract version than this instance speaks, or is not a whole number. Nothing was done.

application/json
  1. response

An error response.

error*

What went wrong.

rate_limited: you sent too many requests. Wait for the number of seconds in Retry-After, then try again.

application/json
  1. response

An error response.

error*

What went wrong.

internal_error: Marfa failed in a way it didn't expect, and the request may not have completed. Read what you changed before you repeat a write.

application/json
  1. response

An error response.

error*

What went wrong.

write_contention: the database was busy, and Marfa couldn't complete the request in time. Nothing changed. Try the request again. While a restore runs, details.reason is restore_running.

application/json
  1. response

An error response.

error*

What went wrong.

insufficient_storage: the disk that holds the instance's data has no room for the request, or the request would leave less free than the instance keeps in reserve. Nothing changed, unless details.write_outcome is unknown, which means the write may have landed: read what you changed before you repeat it. Free space on the disk, then try the request again.

application/json
  1. response

An error response.

error*

What went wrong.

curl -X GET 'http://localhost:8600/owner/passkeys'
About errors
{  "data": [    {      "id": "01a10129-3c7a-7b48-9d15-5e0f2a6c8d31",      "name": "Laptop",      "created_at": "2026-10-03T09:30:00.000Z",      "last_used_at": "2026-10-05T14:12:08.000Z"    }  ],  "next_cursor": null}