Integration recipes

Useful links.
Useful workflows.

Start with one action that saves you a little work.

Save links submitted through a form

1. Create an API key in Settings → Integrations and copy it right away: it is shown only once.
2. Add an HTTP request after your form’s submission trigger.
3. Use POST, the URL and headers below, and map the submitted URL, title, and note into the JSON body.
4. Test with a disposable link and check it in Pinport before enabling the workflow.

POST https://pinport.app/api/v2/bookmarks
X-Api-Key: YOUR_API_KEY
Content-Type: application/json

{
  "url": "https://example.com/contrast-checker",
  "title": "A contrast checker for the redesign",
  "note": "Suggested during our planning meeting",
  "tags": ["Website redesign", "Tools"]
}

Keep the API key in the automation tool’s secret storage. Do not put it in a public form or browser script. Repeated create requests create duplicates: if the trigger retries, track processed submissions, or check for the URL first with /api/v2/bookmarks/search?type=keyword and skip the create when it is already saved.

React when a bookmark is saved

Use a bookmark.created webhook to send a newly saved link to another tool, such as a personal task inbox or a private reading log.

1. Create a webhook receiver in your automation tool and copy its URL.
2. Add that URL in Pinport’s integration settings, select bookmark.created, and configure a secret.
3. Verify the webhook signature before trusting the payload. Filter by a tag if the workflow should handle only certain links.
4. Read the title, URL, note, and tags from the event data, and create the destination item.
5. Track the event’s id so a repeated delivery does not create the item twice.

Bulk imports produce bookmarks.imported events, rather than one bookmark.created event per link. Use the returned bookmark IDs with the API if your workflow should process an import. See webhook payloads and verification.

Build a project reference list

Request the bookmarks for a project tag from a server or automation tool. Format the returned titles and URLs for a private project document. Use a schedule if you want to refresh it periodically.

GET https://pinport.app/api/v2/bookmarks?tag=Website%20redesign&limit=100
X-Api-Key: YOUR_API_KEY

The response contains data and nextCursor. When nextCursor is not null, request the same URL again with &cursor= and that value until it is. Adding another tag parameter narrows the result to bookmarks with both tags. A filter in your private library does not itself publish a shareable collection.

Keep a copy of your library in sync

Keep a nightly backup, a page in your notes app, or a links section on a personal site current without downloading the whole library every time. The changes endpoint returns only what changed since your last sync.

1. Run the request below with since=0 the first time to fetch everything.
2. Apply changed to your copy, and remove the ids listed in deleted.
3. Store the returned version. If hasMore is true, request again with that version before finishing.
4. Next time, pass the stored version as since.

GET https://pinport.app/api/v2/bookmarks/changes?since=0
X-Api-Key: YOUR_API_KEY

Deleted bookmarks are reported as ids for 30 days. A copy that has not synced for longer than that should start again from 0. See the changes endpoint in the API reference for the response shape.

In your automation tool

Every recipe above maps onto the generic HTTP and webhook building blocks in your platform. Use these names to find them, and store the API key and webhook secret as a credential rather than pasting them into a step.

Build your own application

Use the API reference for pagination, filters, and write operations. Use the webhook guide for signatures and event shapes. Handle 429 responses with backoff, keep writes idempotent in your own workflow, and test failures as well as successful requests.