Find answers to frequently asked questions
Owners of the organization can go to the home page. Click "Users" to view the users in the organization. From the drop down menu on the right, click on "Invite User" and enter the required information. An email will be sent to the user to invite them to the organization.
No. Each user only needs one auth token for all services.
The API limits requests to 150 requests per 10 seconds.
The Data Axle Status Dashboard shows the uptime of each API.
Data Axle takes security and privacy seriously. Read more about Data Axle Security.
Download a list of fields and their descriptions at the Data Dictionary.
You will receive an email when new files are ready. Use the File Delivery API to automate detection of new files.
Files are compressed using gzip. No other compression options are available.
Before publishing, an automated quality system reviews each delivery for abnormalities. For new and ad-hoc deliveries, Data Axle employees manually verify each delivery.
The File Delivery API provides an MD5 hash for each file, can be used to perform checksum integrity.
Large deliveries are split into files of about one million records each, for manageability.
Files can be read in any order.
Incremental Files begin generation after 8:00am UTC. File generation times vary depending on the file size.
Weekly Incremental Files begin generation at 8:00am UTC on Monday.
Import Incremental Files in chronological order to ensure that you end up with the most current data.
Process the monthly file as soon as it is available, and make further updates with the Incremental Files.
Monthly files are typically available between the 1st and the 5th of each month. Weekly files generate every Monday at 8:00am UTC. Daily files generate every night at 8:00am UTC.
Use the File Delivery API once per hour to automate this process.
No, filters can be applied in any order.
Only filters using the equals predicate are case sensitive.
The Search API defaults to 10 records per request. You can use the limit and offset parameter to return more results. If you regularly need to return large sets of records, use the Scan API.
The results of your search will change as records are updated and added to the database. You may see records added or removed from future responses. Results may also return in a different order. You can change sorting behavior by applying a sort parameter to your request.
Search API returns a maximum of 100 records per request while the Scan API allows you to scroll through all records that meet your criteria.
The query parameter is not supported in the Scan API.
The initial response includes the number of records that meet your criteria. Use the Insights API to preview detailed counts.
It depends on your use case and volume of suggestions. The Feedback UI requires someone to log in and manually suggest changes. The Submission API is used for large volumes and a way to connect your application to Data Axle.
Submissions are routed to our data associates who typically resolve feedback within 24-48 hours.
Poll the Submission Results API anywhere from once per day to as frequently as you send submissions, depending on how frequently you need the results back.
We recommend 100 submissions or less, per bulk request.
Yes, the API supports submissions to correct duplicates. This can be done by suggesting a value in the
duplicate_of attribute or by commenting on the
What is the latency between the response and the availability of the updated record in deliveries? Is there a cutoff date for accepted changes to appear in files?
There is no latency between when a record is updated and when it can be delivered through files. Changes only need to be applied before the delivery begins generating.