Gitlab Trigger API returns 404

Question

I created a trigger (using settings/ci_cd page). The instructions below the trigger tell me to call it using version 3 API (of course, I set the token variable to the token stated under the trigger section):

curl -X POST \
     -F token=${TOKEN} \
     -F ref=master \
     https://gitlab.com/api/v3/projects/2313008/trigger/builds

Which only returns:

{"error":"404 Not Found"}

I also tried to follow the API v4 documentation:

curl --request POST \
     --form token=${TOKEN} \
     --form ref=master \
     https://gitlab.com/api/v4/projects/2313008/trigger/pipeline

which returns the same error.

Are there any additional settings required?

Yes, I am. Also I would expect to get some other Error then 404. — nik, Mar 13 '17 at 07:15
Well, 404 is pretty clever taken you don't want someone to enumerate the projects you have on your machine. — Jakub Kania, Mar 13 '17 at 16:53

score 14 · Answer 1 · answered Feb 06 '18 at 13:41

14

I had the same issue, but I was using Personal Access Token instead of Pipeline trigger token!!

You can generate this token inside your project repo CI/CD settings.

answered Feb 06 '18 at 13:41

Mohsen Mirhoseini

8,454
5
34
59

score 0 · Answer 2 · answered Apr 09 '17 at 08:43

0

I retried the same request today, now it works. Probably there has been some problem with the gitlab.com.

answered Apr 09 '17 at 08:43

nik

2,114
3
22
43

Gitlab Trigger API returns 404

2 Answers2