Hello, and welcome to the Pixel Directory API guide. Even though I suck at writing API documentation, I'll try my best to help you.
This document-type-thingy is for the people who would like to develop an application (hey that would be cool btw.) using the Pixel Directory, or just are bored and want to read something.
making calls
Every API call is made to http://www.studioxenix.com/directory/api/[function name]. If you need to submit something, it's done using standard HTTP POSTs. When you get something, unless the server is down, it's in JSON.
how the grid works
To not download each and every image file every time the user visit the page, a static image containing all the boxes in their places is transmitted, and used as a background image. If the user uploaded a GIF file, it's downloaded and placed after getting the background image.
how the drawing mode works
If the user chooses to draw it's pixel-icon-thingy online, the HTML5 canvas used to preview the drawing is used to convert the image to base64, and submitted along with the data.
Used to get the background image
"status": string
Always returned. "OK" if there are no problems, "DOWN" if there was a server error.

"gifs": object
Returned if there are GIFs in the grid. Each key specifies which box the GIF should be put into.
To get the GIF, just use
http://www.studioxenix.com/directory/pixels/[box id].gif

"image": string
Base64-encoded background image
Used to get the box data
"status": string
Always returned. "OK" if there are no problems, "DOWN" if there was a server error.

box object: object
Rendered for each box that exists. Has the following values:
unique id of the box (eg: 102)

description text of the box (eg: My Brilliant Blog)

the URL where the box should take the user to
It's your job to place the boxes in their proper places: starting from 0, ending at 944, the boxes jump to the next line every 35th box. The server does not return any X/Y data. Remember the one pixel space between each box.