Wema API test fail
I’m working with Wema onboarding open API and i have been trying to test and API before i use it in my project but I keep getting the
error:
Internal Server Error => Value cannot be null. (Parameter ‘client’).
Here is the request body, I’m still getting the error even after I have filled the body properly with the required credentials.
How to properly design APIs for the following flow
I have a flow for which I’m designing apis and I’m not sure I made the best choice.
The use-case is as follows:
I’m providing a service for users that have boxes which contains bottles of shampoo. I need to insert the bottles into a container with some limitations, the main is that all bottles from a certain box will be shipped in the same container.
How API Calls work when published to the internet
Right now, I am working on an NFL analytics website that uses a lot of data and my main source of getting all this data is through fetching it from an Api. The Api I am using is not my own Api and I am limited to 10,000 request per day. My websites probably not even a quarter of the way done and in the past 24hrs I have made 2,800 requests. So, to go into more detail about my question in the title, once my website is published to a server and users can now access my website. Every time a user accesses the website is it going to make a lot of requests to the API or is the data I got from the API already stored on the server and the users getting the data from the server not the Api. Basically, is the developer the only one requesting data from the Api or is the user also making those request every time your site loads.
Bullhorn Api: query/NoteEntity doesn’t work when one to many relation entity specified
Bullhorn Api Question NOTE to Admins: I have asked this question on Bullhorn forum but no answer that is why asking here. query/NoteEntity?BhRestToken={{BhRestToken}}&fields=note(id,action)&count=50&start=0&where=note.dateLastModified>1720950000000 Above call works fine but following doesn’t, difference is that I have specified one to many relation entity candidates in following query/NoteEntity?BhRestToken={{BhRestToken}}&fields=note(id,action,candidates)&count=50&start=0&where=note.dateLastModified>1720950000000 I get “An internal error has occurred” in above call. […]
Best way to send multiple images through API: one call per image or one call for all images
I´m debating between these two options:
rest api: standard way of requesting required input information before post
This is not a technical problem but more of a style/ best practice question: consider a simple Rest API like this:
Is the Nestoria API still operational in 2024?
I’m trying to use the Nestoria API for retrieving real estate listings, but I’m consistently getting “unknown location” errors even for valid locations like “London” or “Barcelona”. Here is an example of the request I am making:
Is it RESTFUL to have additional flags/keys in an object that are not part of the resource? For POST/PATCH
I have an api to create a ticket for a given component_id, POST /api/ticket
that takes an input of (“component_id”, “ticket_number”, “ticket_date”).
Rest api best practice when dealing with duplicate resources
Let’s consider an api for some kind of tchat application and that can provide 2 kinds of resources : Room
and User
.
Should I fetch parent resource along with nested resources in one call, fetch them in separate calls, or both (REST API)?
I have an API design question. If I have a resource with nested resources and half the time I need to fetch the parent along with the nested resources from the client, should I use one call to fetch these resources or would it be better (in terms of design) to fetch them in separate calls?