nimblecrm/api-docs

API documentation

api-docs's Issues

v1/contact

This endpoint returns a 404, has it been depreciated or changed?

Client error response
[status code] 404
[reason phrase] Not Found
[url] https://api.nimble.com/api/v1/contacts?access_token=REDACTED
[request] GET /api/v1/contacts?access_token=REDACTED HTTP/1.1
Host: api.nimble.com
User-Agent: leaderboarded.com
Content-Type: application/json

[response] HTTP/1.1 404 Not Found
Content-Type: text/html; charset=UTF-8
Date: Fri, 01 Feb 2013 10:02:44 GMT
Server: nginx/1.2.6
Content-Length: 69
Connection: keep-alive

404: Not Found

Problem creating "activities" or "contact notes"

Hi Everybody,

I have successfully created/added "contact" on nimble by sending all parameters passed as JSON in request body and it is appearing fine in nimble.

However, when I create/add "activities" or "contact notes" using api, I will get the below mentioned error.

My request is: {"contact_ids": ["50c07a69e5ef834edb000080", "50c07a53084abd5f61000aac"], "note": "Just contact note, with some longer text", "note_preview": "Just contact note"}

And I always get the same below response:

{ "message": "Validation errors", "code": 245, "errors": { "note": { "message": [ "This field is required." ] }, "contact_ids": { "message": [ "This field is required." ] }, "note_preview": { "message": [ "This field is required." ] } } }

Please advise.

I think it is api isuse that one of the nimble support guy mentioned in the link (https://developers.nimble.com/forum/create-custom-fields-probjem). I have tried the way that nimble user "bear-z" mentioned in the link "https://developers.nimble.com/forum/create-custom-fields-probjem" but it did not work out. Please advise on this so that I can move forward.

Any help would be highly appreciated.

Thanks
Asim

Create contact note request can't be propagated with created date

Current API version doesn't support to propagate 'created' field in create contact note request.
Do you have any plans to change API contract to support such field?

Freshdesk integration broken OAuth2 redirect_uri_mismatch

after the switch to the new OAuth for nimble,
it seems like there is no token in callback for the auth request.

generated uri
http://api.nimble.com/oauth/authorize?response_type=code&redirect_uri=https%3A%2F%2Flogin.freshdesk.com%2Fauth%2Fnimble%2Fcallback&client_id=***************

Please work with Freshdesk to resolve this minor issue as soon as possible, as right now the integration is completely broken (even for already authorized integrations)