Access API

Create a login link

Generate a temporary login link for a user owned by your vendor account.

POST/login_links

Overview

Create a reusable-until-expiry login link for an eligible account user. This is an account login capability and should not be substituted for a participant’s session-specific signing link or team onboarding link.

Before you start

The user must exist and belong to this vendor. Generate the link from a trusted backend and deliver it privately.

  1. Resolve the user

    Verify the intended account-owned email.

  2. Generate the link

    Request a fresh login link from your backend.

  3. Deliver and expire

    Send privately and request a new link when the previous one expires.

Parameters

FieldRequirementDescription
email
string · email
RequiredThe email of the existing user whose vendor ownership matches the API key.

Request example

Use a server-side API key. Replace example IDs and values before using this request in an approved test environment.

curl --request POST \
  --url 'https://app.bluenotary.us/api/integrationsv2/login_links' \
  --header "Authorization: Bearer $BLUENOTARY_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "email": "sam@example.com"
}'

Response

200 · Example success Illustrative values in the current response shape.

RESPONSE
{
  "success": true,
  "login_link": "https://app.bluenotary.us/REDACTED_LOGIN_LINK",
  "expires_in": 43200
}
  • expires_in is measured in seconds: 43200 seconds is 12 hours.
  • The login link is reusable until it expires. It is not a one-time link.
  • The handler uses email and vendor ownership. Do not add undocumented password or assertion requirements to this example.
  • Login links are credentials. Do not expose them in a public page, shared support ticket, or telemetry.

Errors & recovery

StatusWhat happenedWhat to do
422Missing emailProvide email in the JSON request body.
404User not foundConfirm the user already exists.
403User belongs to another vendorUse an eligible user owned by the authenticated account.
401Authentication failedUse a valid API key.

Explore the response

Response simulator

LOCAL EXAMPLE

Explore the example response without an API key. This does not send requests or validate your account configuration.

Keep building