Common error codes, pitfalls, and how to resolve them.
If you run into issues integrating with the Field Nation API, use this guide to diagnose and resolve common errors.
| Code | Meaning | Action |
|---|---|---|
400 | Bad Request | Check your JSON syntax and data types. |
401 | Unauthorized | Check your token validity. |
403 | Forbidden | Check your user permissions (Scopes). |
404 | Not Found | Validate your IDs. |
429 | Too Many Requests | Slow down. Implement exponential backoff. |
500 | Server Error | Retry once. If it persists, contact support. |
Symptom: You send a date, but get a validation error.
Fix: Ensure you are using the precise { "utc": "YYYY-MM-DD HH:mm:ss" } object structure. Plain strings like "2023-01-01" are often rejected in strict fields.
Symptom: You are testing in Sandbox using IDs (Type of Work, Template, Project) from Production. Fix: IDs are unique to each environment. You must recreate your setup (Projects, Templates) in Sandbox and use those new IDs for testing.
Symptom: Used to work, now returns 401.
Fix: Access tokens expire after 1 hour. Your code must handle the 401 response by using the refresh_token to fetch a fresh access_token automatically.
Symptom: You have a valid token, but cannot modify Financials or Users. Fix: The API user associated with your credentials likely lacks the specific permission bit (e.g., "Manage Providers" or "View Financials"). Log in to the UI with that user to verify access, or ask an Admin to grant the permission.
Last updated on
