API calls worked with SKY Developer Cohort, Receiving 404 errors after switch to org environment

Zach Woolf

My org admin and I went through the process of loading an app we are working on into our orgs enviornment so we can start testing with our data instead of what is available through the SKY Developer Cohort. All my API calls were working fine before the switch, now I'm receiving

``` [{'message': 'The requested operation could not be fulfilled', 'error_name': 'RequestNotFulfilled', 'error_code': 404, 'raw_message': 'The requested operation could not be fulfilled', 'error_args': []}]```

with every call that is made. Was there a step missed when setting up the app in our environment? What should I be looking at for a solution to make the calls work again?

Zach Woolf

@Zach Woolf
Update:

I went to the consol to test the GET constituent API call that was failing. When I authorize through our orgs environment I receive the 404 error. When I authorize the call through the SKY environment, everything works fine.

Is there potentially something wrong with my access to our orgs environment?

Zach Woolf

@Zach Woolf Figured out the problem. I was looking at the wrong part of a constituent profile to pull data to do the call with. This one's on me.