How to use the HEDEX Web Service API’s
Index
- General Philosophy – How this is different from REST?
- Explaining the GETs, POSTs, and outbound POSTs (push)
- How is the tenant ID used?
- When should you use the “top-level” POST’s versus the “lower-level” POSTs?
- Is there a difference in a POST for a create or an update?
- How do you know what primary keys to send?
- What fields are required in a POST?
- If nothing is required, then what do I know what to send?
- How can I tell what valid values to send (enums) for fields?
- How do I know what systems my POSTS are going to be routed to? Can I control it?
- How do I know if my POST worked and where it went?
1. General Philosophy – How this is different from REST
<to be added>
2. Explaining the GETs, POSTs, and outbound POSTs (push)
<to be added>
3. How is the tenant ID used?
<to be added>
4. When should you use the “top-level” POST’s versus the “lower-level” POSTs?
<to be added>
5. Is there a difference in a POST for a create or an update?
<to be added>
6. How do you know what primary keys to send?
<to be added>
7. What fields are required in a POST?
<to be added>
8. If nothing is required, then what do I know what to send?
<to be added>
9. How can I tell what valid values to send (enumerated/enum) for fields?
<to be added>
10. How do I know what systems my POSTS are going to be routed to? Can I control it?
<to be added>
11. How do I know if my POST worked and where it went?
<to be added>