Using the new bulk apis?

[jim_jim_lam_Lam]

Has anyone been able to use the new bulk apis?​ Whenever I try to use the create job or get job (or even the sample call provided in the docs), nothing is returned to me - even though I get a 200 response status.

[Neil_Robertson6]

No errors for me following the docs, I can successfully request/grab the data - but - the mix of plain text separated by comma and JSON is extremely odd and useless IMHO.   For now I would stick to using a connector like Kingswaysoft (though I will think about how I can use this API going forward)

[jim_jim_lam_Lam]

Figured it out, /rest/ isn't supposed to be there.

[Anonymous]

Did it work after you correct the URL? I can submit the request, but the job itself is stuck in "Queued" status.

See: Bulk API: extracting activities job stuck in Queued status

[jim_jim_lam_Lam]

Hi Ko-Chih! I didn't attempt to go any further, but I would imagine that it would eventually start processing after some time. Per the document, it says: This will respond with a status of “Queued” after which it will be set to “Processing” when there is an available export slot.

Perhaps someone from Marketo can chime in on what an "available export slot" means - is it a global Marketo shared slot or is it specific to our own Marketo instance?

[Kenny_Elkington]

Bulk Extract has its own queue within each instance, so it shouldn't be blocked by other job types.

[Anonymous]

Someone else posted this issue Bulk API: extracting activities job stuck in Queued status I am having the same problem, after I create a job and then queue it for processing the job just seems to sit in the queue and never moves to processing or complete. Going to open up a case for it but it seems to potentially be a bigger issue?

[Kenny_Elkington]

We've got an engineering escalation open now and are looking into the issue.

[Kenny_Elkington]

You know what I need, Yim.

[jim_jim_lam_Lam]

Hi Kenny. Can you direct me into finding what you are asking for? I am using this exact example, and there is nothing returned to me.

[Kenny_Elkington]

Of course, there was a typo in the doc.  The path to create a job is "/bulk/v1/leads/export/create.json"  not "/bulk/v1/leads/export.json".  I've corrected the docs.

[jim_jim_lam_Lam]

I noticed that too as I was looking through the endpoint page, but yields the same result:

[Anonymous]

I was able to get it to work with the corrected URL and using a POST:
I also set the following Headers: 

Content-Type:  application/json

Accept: application/json

{

    "requestId": "43fb#15cc17b2d66",

    "result": [

        {

            "exportId": "dc51eba7-741d-4f85-bb56-52efda334b27",

            "format": "CSV",

            "status": "Created",

            "createdAt": "2017-06-19T17:51:34Z"

        }

    ],

    "success": true

}

[Justin_Norris1]

Maybe Kenny Elkington​ can help on this one.

[Anonymous]

I am also unable to get this to work.

When I try and use a POST (as in the documentation example) I get:

{

    "requestId": "f0a2#15cc145664d",

    "success": false,

    "errors": [

        {

            "code": "605",

            "message": "Request method 'POST' not supported"

        }

    ]

}

When I use a GET:

{

    "requestId": "13a38#15cc144eab6",

    "result": [],

    "success": true

}