---
title: "Request a connection"
method: POST
path: "/v1/connections"
tags: ["Connections"]
---

# Request a connection

`POST /v1/connections`

## Request

- Base URL: `https://api.taplio.com`
- URL: `https://api.taplio.com/v1/connections`
- Auth: HTTP bearer

Queues a connection request for `username`; nothing reaches LinkedIn during this request. `scheduled_for` is when the invitation is due to go out, following the account's sending schedule, so it can be minutes away or much later. Calling it again for a recipient already queued answers `200` with the request in flight instead of stacking a second invitation, so it is safe to retry. The invitation carries no note: LinkedIn caps noted invitations far lower than plain ones, and by account tier, so a plain one is far likelier to land. A request the account cannot currently send is refused with `409 connection_request_blocked`, which carries the reason.

## Request body

- object
  - `username` string, required

## Response `200`

A request for this recipient was already in flight.

- Connection
  - `created_at` string, date-time, required
  - `failure_code` string
  - `failure_reason` string
  - `message` string
  - `scheduled_for` string, date-time
  - `status` 'pending' | 'sent' | 'failed' | 'cancelled', required
  - `username` string, required

## Other responses

- `201`: Connection request queued.
- `400`: Validation failed.
- `401`: Missing or invalid API key.
- `402`: Subscription payment failed.
- `403`: Subscription does not allow this request.
- `404`: Resource not found.
- `409`: Resource state precludes this request.
- `422`: Request semantically rejected.
- `429`: Rate limit exceeded.
- `500`: Internal server error.
- `503`: Upstream unavailable.

---

[API](https://skmtc.dev/taplio/apis/taplio-rest-api.md) · [All operations](https://skmtc.dev/taplio/apis/taplio-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/taplio/apis/taplio-rest-api/revisions/961302019f3f?raw)