Get Opportunities REST API requires filterType, even if doc says it's optional? | Community
Skip to main content
A
Anonymous
June 25, 2015
Question

Get Opportunities REST API requires filterType, even if doc says it's optional?

  • June 25, 2015
  • 2 replies
  • 2733 views

Documentation at Get Opportunities » Marketo Developers  states that filterType is optional; but when I try using that API without specifying any filterType, I get:

{

    "requestId": "352d#14e2c4952c5",

    "success": false,

    "errors": [

        {

            "code": "1003",

            "message": "filterType not specified"

        }

    ]

}

Documentation or code issue? It would seem quite limiting not being able to retrieve Opportunity records unless you enumerate their Marketo or external ID (which are the only searchable fields returned by Opportunity Describe)...

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

A
Anonymous
June 25, 2015

Unfortunately the same seems to be true also for other objects, like opportunity roles and custom objects...

John_M
Adobe Employee
John_MAdobe Employee
Adobe Employee
June 25, 2015

Hi Carlo

What other examples have you found? I'll follow up with the documentation team and get back to you on this. Thank you for noticing and posting on this!

A
Anonymous
June 25, 2015

Opportunities, Opportunity Roles and all Custom Objects.

If filterType is mandatory, and the filter can't be based on creation/update timestamps (as it doesn't seem to be possible to do), this makes the REST APIs for access to those objects *extremely* limiting...

John_M
Adobe Employee
John_MAdobe Employee
Adobe Employee
June 25, 2015

Carlo - For opportunity, filterType is *required*. The docs have been updated. Can you tell me what other specific doc pages and I'll look into those as well?

John_M
Adobe Employee
John_MAdobe Employee
Adobe Employee
June 26, 2015

Get Opportunity Roles, Company, and Custom Object have been updated as well.

A
Anonymous
June 26, 2015

BTW, if filterType is required, then of course also filterValues is...

I understand that's not available today, but in general, it would be great if I could specify an initial nextPageToken equivalent to what's returned by the activities/pagingtoken API in the context of the Activity object, and then iterate through the objects mentioned above without any further filter information.

Terms & ConditionsAccessibility statement

Loading footer...