You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought maybe it might be beneficial to start with a benign and easy API endpoint for GET requests just to illustrate a basic configuration. This would allow us to maybe assist the end user when they are setting up configuration. I also don't mind writing some overall documentation that's more advanced for the actual Help section. Let's start with the Star Wars API
If I use https://swapi.co/api/people I see several results of which I can append a number to the URL and get a result or I can simply see all the results. https://swapi.co/api/people/1
I thought maybe it might be beneficial to start with a benign and easy API endpoint for GET requests just to illustrate a basic configuration. This would allow us to maybe assist the end user when they are setting up configuration. I also don't mind writing some overall documentation that's more advanced for the actual Help section. Let's start with the Star Wars API
Endpoints
https://swapi.co/api
If I use
https://swapi.co/api/people
I see several results of which I can append a number to the URL and get a result or I can simply see all the results.https://swapi.co/api/people/1
Walkthrough
Walk me through the process of setting the people endpoint up with WSDATA to store the "species" field in a WSFIELD for a content type.
The text was updated successfully, but these errors were encountered: