Updating an existing VersionEye project using API

The VersionEye API enables you to create a project using the API. All you need to do is use POST to send your project file to the “/v1/projects.json” endpoint. VersionEye then creates a new project for it and returns a JSON with the used libraries and any outdated information.

There is already an add-on for the Symfony Developer Toolbar:

https://github.com/mattsches/VersionEyeBundle

versioneyebundle_screenshot

And one for the Zend Dev. toolbar:

https://github.com/Ocramius/VersionEyeModule

These modules send your composer.json file to the VersionEye server.  Unfortunately, the first version created a new project at VersionEye each time there was a post. This is not the desired behavior. We added a new endpoint to the API which enables API developers to update existing projects.

The process now looks like this. First, you upload the composer.json file via POST to this resource: “/v1/projects.json“. In the response, VersionEye returns a “project_key” for the project. Next, you send the composer.json file via POST to this new resource: “/v1/projects/{project_key}.json“.

Screen Shot 2013-03-25 at 10.05.20 AM

The new endpoint, “/v1/projects/{project_key}.json”, does not create a new project. It only updates an existing project. Please use it in the future to update an existing project.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s