“message”: “Response data is too big. Please refine your parameters to get a smaller response”
This response message is due to the fact that Realogy API processing services place restrictions in the size of the response returned by the APIs in order to ensure optimal processing latency and throughput for the API calls for all types of consuming applications avoiding any time out related errors that may occur in fetching large amounts of data. To ensure this error is not seen, please refine your request parameters (time period of data selection, other filter criteria etc.) to ensure less data is fetched by the API end point in a single call. For questions, please reach through Support section in the portal for the specific API that you are facing this challenge.
- Send Client ID, Client Secret and Scope to the Realogy Okta Authorization Server's Token Endpoint (Access Token URL).
- If the credentials are valid, the AS returns an access token to the client application with a scope set to the “App ID URI” of the requested Realogy REST API.
- Pass the valid access token and subscription key when calling protected API.
- After validation, the Realogy API returns the result (JSON or XML).
No. This should never be stored in a Mobile App or Native App. Always store the client secret key securely. If you suspect that the secret key has been compromised, then you can request for another client secret.
Please ensure boundary is set and Content-Type is 'multipart/form-data'.
Once an App is created, its name cannot be changed. In case you want to use another App name, we suggest to create a new one.
Once you have access to the Realogy API product using "Get Access" to a specific environment, you can test the API using Postman collection for the specific API product. You can access Postman collection in "Essential Reads" section for a specific API product.
If you need any help or have questions about testing for a specific API product, please contact us.