Source
Data access, export & self-hosting — found from sitemap — Parse.ly
Checked for Parse.ly on 17 Nov 2026
- Page
- https://docs.parse.ly/api/api-overview/
- Checked
- 17 Nov 2026, 15:14 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:de6be659a58297ec0de7d727384a58315546a61323f76aa6c4a41be601c2d43a
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
API root URL Report an error
“The root URL for all Parse.ly API requests is https://api.parsely.com/v2/”
-
API requests http get Report an error
“Most of our requests are HTTP GET requests. All requests support the following parameters:”
-
API authentication Report an error
“apikey the Site ID (API key) specified in your Parse.ly JavaScript tracker; Required for all requests. secret this parameter is required for every request unless otherwise noted and should contain the secret token obtainable from the API Settings page.”
-
Jsonp callback Report an error
“callback to support the JSON-P standard, all GET requests can take a callback parameter which will wrap the JSON response in the specified callback function, allowing easy integration into web frontends via JavaScript. Parse.ly also supports Cross-Origin Resource Sharing.”
-
API response format Report an error
“Successful responses are JSON documents using a “data envelope” format”
-
API content types Report an error
“Posts: Content pages with associated metadata, URL, and metrics Metas: Authors, Sections, Tags, etc. with associated metrics”
-
API pagination Report an error
“The links object contains pagination links. It will always contain a first key, with a link to the first page. A next link will be present if more results are available, otherwise null. A prev link will be available on all pages past the first.”
-
API accuracy vs dashboard Report an error
“The API’s numbers will not match exactly the numbers in our dashboard. This is because the dashboard (and the reports/exports subsystem in the dashboard) always makes a strong effort to get “the most exact counts possible”, whereas the API occasionally accepts a small error rate (1-2% typically) in the name of performance/speed.”
-
Raw export available Report an error
“If you are interested in programmatically exporting exact counts of all your data, you should explore our raw data export options by reaching out to Parse.ly Support.”
-
API error encoding Report an error
“As a matter of practicality, “normal” errors return HTTP Status Code 200 to your client, but encode the error in the JSON document that is returned.”
-
Metadata endpoint secret Report an error
“Note: The /metadata endpoint uses a distinct write-only secret value.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Agency Developer Traffic, sources & campaign reports
- The Agency Developer Data access, export & self-hosting
- The Data Protection Officer Traffic, sources & campaign reports
- The Data Protection Officer Data access, export & self-hosting
- The E-Commerce Marketing Lead Data access, export & self-hosting
- The Growth Analyst Data access, export & self-hosting
- The Public-Sector Site Owner Data access, export & self-hosting
- The Skeptic Data access, export & self-hosting