Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error response format differs from the convention used by other ORS backends #37

Open
aoles opened this issue Jun 12, 2018 · 0 comments
Assignees

Comments

@aoles
Copy link
Member

aoles commented Jun 12, 2018

The format of errors returned by the pois API differs from the one used by the rest of ORS endpoints. It is an object with code and message at top level

{
    "code": 4000,
    "message": "Invalid JSON object in request"
}

rather than a JSON object with code and message nested in error such as for directions, for example:

{
  "error": {
    "code": 2001,
    "message": "Parameter 'profile' is missing."
  },
  "info": {
    "engine": {
      "version": "4.5.0",
      "build_date": "2018-03-26T13:41:46Z"
    },
    "timestamp": 1528809944677
  }
}
@TimMcCauley TimMcCauley self-assigned this Aug 7, 2018
nilsnolde added a commit that referenced this issue Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants