-
Notifications
You must be signed in to change notification settings - Fork 3
Add docs related to reporting data export #267
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
Add docs related to reporting data export #267
Conversation
fccb5ad to
2ddcc8e
Compare
| "/export/reporting_data/enqueue": | ||
| post: | ||
| summary: Enqueue a new reporting data export job | ||
| tags: [Export] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this tag achieves the grouping rather than needing to nest the resource name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is for grouping.
descriptions/0/api.intercom.io.yaml
Outdated
| message: "Export job not found for identifier: job1" | ||
| schema: | ||
| "$ref": "#/components/schemas/error" | ||
| '504': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
504 is specific to timeouts. Is this a known issue that comes up, and if so could we explain that in the description?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated the docs after updating the API. Thanks for pointing out.
| "/export/reporting_data/get_datasets": | ||
| get: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually wouldn't have get in the path as well as being the HTTP method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But if it matches the behaviour we can update the docs for now. While it's in Unstable though we could change to align with other API endpoints.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@steve-henry yeah that's a good point we shouldn't have get in the name of the resource according to REST conventions. It should have been like
GET /export/reporting_data/datasets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I think that would be clearer and more consistent with the rest of the APIs
63b64dd to
a6833b9
Compare
a6833b9 to
d771cd3
Compare
The aim of this PR is to add API docs related to reporting data-export.
We are documenting below requests handled by
app/controllers/api/v3/export/reporting_data_export_controller.rbcontroller.POST /export/reporting_data/enqueueGET /export/reporting_data/{job_identifier}GET /download/reporting_data/{job_identifier}GET /export/reporting_data/get_datasets