Documentation
API Authentication
Authenticate API requests and connect downstream systems with governed access.
Best for: Developers, integration engineers, and solution architectsLast updated: 2026-03-21
Guide overview
Keep access scoped by environment and workflow responsibility. Authentication design should support safe automation, auditability, and clear connector ownership.
Use dedicated credentials per integration instead of shared personal accounts.
Store tokens in your deployment environment and rotate them on a defined schedule.
Pair API access with approval and validation rules so automations do not publish incomplete records.
Log request context by connector to simplify issue triage and retry handling.
Example
curl -X GET 'https://api.lynkpim.app/v1/products' \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Accept: application/json'Related docs and next steps
Need implementation support?
Use the docs as your rollout blueprint, then connect them to pricing, tools, and solution pages when you need a deeper implementation plan.