I'm able to get an access token from workday, but I'm having trouble with understanding the resource endpoints. I've not been able to get any of the following to work. The ID I'm using does exist in the tenant.
ONE - this workday article, https://community.workday.com/articles/665624, says REST API URLs must follow this path format:
(basepath)/api/(service)/(version)/(tenant)/(resource)
my request - https://(domain)/ccx/api/customerAccounts/v1/(tenant)/customers/(id) --> 404 not found
TWO - The swagger file for customers says the base URL is:
https://(tenant hostname)/customerAccounts/v1
my request - https://(domain)/ccx/customerAccounts/v1/customers/(id) --> 404 not found
THREE - The rest client configuration says the Rest endpoint is: https://(domain)/ccx/api/v1/(tenant)
my request - https://(domain)/ccx/api/v1/(tenant)/customerAccounts/v1/customers/(id) --> 404 not found
Does anyone know what the URL endpoints should look like? A specific example would be appreciated.
Thanks!
Format is as follows. My issue appears be security related.
Am still having issues here with standard objects.
https://(domain)/ccx/api/customerAccounts/v1/(tennant)/customers/(ID)
for custom objects. this is confirmed to work.
https://(domain)/ccx/api/v1/(tennant)/customObjects/(objectAlias)/(ID)
Related
I was using geoserver api to create a new user for my application, after I upgraded my geoserver to 2.18.2 the same code doesn't work any more.
until now I used this route which was working absolutely fine:
http://geoserver:8080/geoserver/geofence/rest/usergroup/service/jdbc_userservice/users
If i still use this route, I get this error:
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Therefore I tried this route which I found in their api docs:
localhost:8080/geoserver/rest/security/usergroup/users
but I get this error:
Type Status Report
Message Forbidden
Description The server understood the request but refuses to authorize it.
any hint or docs about this issue will be appreciated.
Referring to TopDesk's Login API,
I'm using PostMan to be authorized.
GET http://www.topdesk.com/api/login/person
Authorization: Basic <base64 encoded password removed>
However, I get 404 Not Found Error and Content-Type is html.
I was expecting it to be either:
200 - OK
401 - Unauthorized
500-Internal-Server-Error
in JSON format.
Any ideas?
Looking at the docs I don't think http://www.topdesk.com/ is the base URL for the API. I don't know what your specific API URL is.
Do you have a set up like the screen shots in this example, if so then the url will be available in that
A 404 code suggests the URL is wrong - http://topdesk-url/tas/api/login/person is the one in the API docs which is slightly different than the one you provided in the question.
The base path that you’re using and the /tas/ (this might be a username or account name etc) section is missing from your example request.
http://www.topdesk.com is not a real TOPdesk instance, it's just a website. A real TOPdesk instance's address looks like one of these:
mycompany.topdesk.net (if it is hosted in the cloud)
topdesk.mycompany.com (if it is hosted locally)
The reason why you got a 404 is because that url simply doesn't exist.
I'm building a web application that needs to search the QCMobile API using the URL endpoint their documentation provided.
API URL
The path for all API resources must start with: https://mobile.fmcsa.dot.gov/qc/services/ The following are the Endpoints
EndPoint Name Query Parameters Example
/carriers/docketNumber/:docketNumber/ /carriers/docketNumber/1515?webKey=jk+k...
My URL is:
https://mobile.fmcsa.dot.gov/qc/services/carriers/docketNumber/402573?webKey=1a7649929fa2....
But I get this json response:
{"links":[],"content":"There is no resource for path /qc/services/carriers/docketNumber/402573"}
Any help would be greatly appreciated.
Kevin
It could be that the endpoint name listed on the specs page isn't correct for docketNumber. I tried your link with my webkey and it didn't work for me either. I replaced "docketNumber" with "docket-number" and I got a complete response.
https://mobile.fmcsa.dot.gov/qc/services/carriers/docket-number/402573.xml?webKey=xxxxx
I'm trying to get task info via Active Collab REST API and have a problem.
I got token by login and password and successfully made a request on next URL's:
GET on https://app.activecollab.com/ACCOUNT_ID/api/v1/projects
GET on https://app.activecollab.com/ACCOUNT_ID/api/v1/projects/1
But I receive 404 on:
GET on https://app.activecollab.com/ACCOUNT_ID/api/v1/projects/1/time-records
I found this endpoint in the documentation
https://developers.activecollab.com/api-documentation/v1/projects/elements/time-records/time-records.html
Could you please explain to me what am I doing wrong?
Thank you very much
Time tracking is not enabled by default per project. You can make sure that you enable it when you create a project (or update project's settings), or check whether it is enabled in your code.
To check if it is enabled, you can probe for 404 on /projects/:project_id/time-records API end point, or you can check for is_tracking_enabled property in response that you get from /projects/:project_id API response.
I'm trying to retrieve all the available sites from the Yodlee API.
As I did for User Registration or Cobrand Login, I tried to obtain the list of available method on the WSDL endPoint.
Basically, I pass this to my yodlee url + / services url :
SiteTraversalService?wsdl
But all I receive is a 404.
Wasabi::Resolver::HTTPError: Error: 404
Does anyone has an idea?
Thanks,
Yodlee Service URL 404s generally happen because the the URL in fact is incorrect.
This can happen because of several reasons.
Either the URL is invalid
The Version was not specified in the Service Url (and the functionality you requested is not available in the fail-over API version).
To check if your URL is valid/invalid you need to enable tracing so you can see the exact request url that went out.
If you're on Windows you may find Fiddler to be very useful for this. (You will need to enable the requirements for sniffing/decrypting SSL Traffic). For other platforms the SDK Guide has some other alternatives.
Once you've ensured that the URL is valid the next step is making sure you're specifying the version.
Newer API functionality is not available in older API Versions. You specify the Version in your Service Url URL which determines the functionality that is available to you. Yodlee versions are appended to the Service Page Url in the form of _Major_Minor (12.0 and 11.1) would be _12_0 or _11_1
Example:
new EndpointAddress(BaseServiceUrl + Name_TransactionDataService + ServiceVersionPrefix)
where
BaseServiceUrl is your base Yodlee url (provided by your rep or Yodlee Dev Center)
Name_TransactionDataServices is say "TransactionDataService"
and VersionPrefix would be your version/sub version in the format of "_12_0" or "_11_1" (12.0 or 11.1).
So your url should look/resemble the following:
https://yodleedomain/yodsoap/services/TransactionDataServices_12_0
(I do not append the ?WSDL to the url).
If you want to test the connectivity to the Yodlee service, do the following --
Invoke -- https://yodleedomain:port/yodsoap/services/listservices