API reference / Connected account
Get one connected account
Written and maintained by The ProspectAPIs team
GET/v1/accounts/:account_id
GET /v1/accounts/:account_id is the ProspectAPIs operation getConnectedAccount, in the Connected account group of the REST API. One connected account by its account_id. Never returns a session. Free. Cost: free; one connected account, never its session. Send your API key as a Bearer token in the Authorization header.
How this fits with the rest of the connected account API, with worked examples, is in the connected accounts guide.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| account_id required | path | string | The account_id from GET /v1/accounts. |
Responses
| Status | Meaning |
|---|---|
| 200 | The connected account. |
| 401 | The API key is missing or invalid. |
| 404 | No account with that id on this key. |
| 503 | Temporarily unavailable. |
Every error answers with the same JSON body, an error string and sometimes a code; the errors page lists each status and when it happens.
200 response fields
The connected account. The body is a ConnectedAccount.
| Field | Type | Description |
|---|---|---|
| connected required | boolean | true when an account is connected. |
| status | string: active, dead, connecting | active; connecting while a sign-in waits for a code or a check; or dead when the session has signed out and needs connecting again. Absent when nothing is connected. |
| account | object | The connected account as the platform names it. |
| account.handle | string or null | The account's public handle. |
| account.name | string or null | The account's display name. |
| egress | string: dedicated, shared_fallback, customer_proxy, none | How the account reaches the platform. Every connected account acts through its own dedicated IP unless you bring your own proxy: dedicated (an IP leased to this account alone), shared_fallback (a shared IP, used only while every dedicated IP is taken), customer_proxy (your own proxy_url) or none. |
| created_at | string (date-time) or null | |
| updated_at | string (date-time) or null | |
| last_used_at | string (date-time) or null | When an action last ran on it. |
| account_id | string or null | This account's id. Name it with account_id on any route that acts on a connected account; optional while the key has exactly one. |
| Header | Meaning |
|---|---|
| RateLimit-Limit | Requests this API key may make per minute. |
| RateLimit-Remaining | Requests left in the current one-minute window. |
| RateLimit-Reset | Seconds until the current window resets. |
Code samples
Each sample sends the same request. Set PROSPECTAPIS_KEY in your environment first. Values come from the spec's examples; replace them with your own.
curl https://api.prospectapis.com/v1/accounts/account id \
-H "Authorization: Bearer $PROSPECTAPIS_KEY"const res = await fetch("https://api.prospectapis.com/v1/accounts/account id", {
headers: { Authorization: `Bearer ${process.env.PROSPECTAPIS_KEY}` },
});
if (!res.ok) throw new Error(`${res.status}: ${(await res.json().catch(() => ({}))).error ?? res.statusText}`);
const data = await res.json();
console.log(data);import os, requests
res = requests.get(
"https://api.prospectapis.com/v1/accounts/account id",
headers={"Authorization": f"Bearer {os.environ['PROSPECTAPIS_KEY']}"},
timeout=30,
)
res.raise_for_status()
data = res.json()
print(data)Billing
The call itself is free, and what it sets up is billed as it runs: one connected account, never its session. Metered spend on the same key is reported after each response in X-Credits-Remaining, and GET /v1/account shows the balance at any time.
Related
The connected accounts guide covers this area end to end. Previous operation: Connect another account. Next operation: Remove a connected account. Every operation, grouped by area, is on the API reference index.
Create a free account to get a key, then run the samples above with your own values.
Was this page helpful?