Fetching by URL

Openhandle's canonical data endpoints use stable platform identifiers:

@username     username
4398626122    stable platform ID
ABC123        platform-native post identifier or Instagram shortcode

SDKs parse supported social URLs locally before making one canonical data request. Raw HTTP clients can fetch the represented resource in one request:

curl "https://api.openhandle.dev/v1/urls/fetch" \
  -X POST \
  -H "Authorization: Bearer $OPENHANDLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.instagram.com/p/Db04otPRpRH/?igsi=NjJteXVldjVmNDdk","freshness":"24h"}'

The response uses the same typed public envelope as the canonical profile, post, story, or highlight operation. Its top-level platform and resource fields identify the returned type, and the Content-Location response header contains the canonical Openhandle path.

URL parsing itself does not contact a social platform. The resolved data read uses the canonical operation's cache, billing, errors, and response mapping, so it is charged exactly once. Unknown domains, shortened redirect links, reserved application paths, and URL formats that do not contain enough identity information return INVALID_URL.