The Basics

cmd=listCases

Parameters
  Optionally takes sFilter (defaults to current filter), cols, and max.
Example
https://kakapo.fogbugz.com/api.asp?cmd=listCases&cols=ixBug,sTitle,ixPersonAssignedTo&max=2&token=04t9123822q4kbba09nt740inhibk2
Returns
  A list of cases returned with data specified by cols.

cmd=adminSetCaseNumber

This sets the next newly created case to start with this case number. For example, if the current highest case number is 35, and you want the next case number to start at 5000, then you can run this command with the value of 5000. Note that you can only use this command to raise the next value, not lower it. Please note that this cannot be undone.

Parameters
Requires ixBug.
Example
https://kakapo.fogbugz.com/api.asp?cmd=adminSetCaseNumber&ixBug=1000&token=04t6193822pekbba09nt74ninuihk2 
Returns
Empty response.

cmd=view

Marks cases as viewed in the FogBugz UI. If ixBugEvent is supplied, will only mark case as being “viewed” up until this bugevent. If omitted, will mark case as being viewed up to the latest bugevent. To mark a case as unread, use ixBugEvent=1

Parameters
Requires ixBug.  Optionally takes ixBugEvent.
Example
https://kakapo.fogbugz.com/api.asp?cmd=view&ixBug=282&token=04t6193822pekbba09nt74ninuihk2 
Returns
Empty response.

cmd=new

Parameters
Takes almost all fields that it is possible to edit through the user interface (and a few more).  See parameters for details. Also accepts ixPersonEditedBy and dt parameters from Site Admins to enable accurate imports with the API. Note that setting ixPersonEditedBy when using the command cmd=new sets who opened the case.
Example
https://kakapo.fogbugz.com/api.asp?cmd=new&ixBug=700&ixPersonEditedBy=12&ixProject=10&sTitle=New%20Case%20Created%20via%20API&sEvent=This%20is%20the%20original%20text%20of%20the%20case%20created%20by%20the%20API.&token=04t6193822pekbba09nt74ninuihk2
Returns
The case number of the newly generated case.  

cmd=edit

Parameters
Requires ixBug. Takes almost all fields that it is possible to edit through the user interface (and a few more).  See parameters for details. Any fields not specified will remain unedited. Also accepts ixPersonEditedBy and dt parameters from Site Admins to enable accurate imports with the API.
Example
https://kakapo.fogbugz.com/api.asp?cmd=edit&ixBug=700&ixPersonEditedBy=12&ixPersonAssignedTo=13&sEvent=Marlene%2C%20could%20you%20take%20a%20look%20at%20this%3F&token=04t6193822pekbba09nt74ninuihk2
Returns
The case number of the edited case.  

cmd=assign

Parameters
Takes almost all fields that it is possible to edit through the user interface (and a few more).  See parameters for details. Also accepts ixPersonEditedBy and dt parameters from Site Admins to enable accurate imports with the API.
Example
https://kakapo.fogbugz.com/api.asp?cmd=edit&ixBug=700&ixPersonEditedBy=12&ixPersonAssignedTo=13&sEvent=Marlene%2C%20could%20you%20take%20a%20look%20at%20this%3F&token=04t6193822pekbba09nt74ninuihk2 
Returns
The case number of the edited case.

cmd=resolve

Note: the UI does not let you change the project, area, assigned to, and category on resolve. The API does.

Parameters
Requires ixBug. Takes ixStatus and almost all fields that it is possible to edit through the user interface (and a few more).  See parameters for details.  Any fields not specified will remain unedited.
Example
https://kakapo.fogbugz.com/api.asp?cmd=resolve&ixBug=700token=04t6193822pekbba09nt74ninuihk2
Returns
The case number of the edited case.  

cmd=reactivate

Parameters
Requires ixBug and takes almost all fields that it is possible to edit through the user interface (and a few more).  See parameters for details. Also accepts ixPersonEditedBy and dt parameters from Site Admins to enable accurate imports with the API.
Example
https://kakapo.fogbugz.com/api.asp?cmd=reactivate&ixBug=700&token=04t6193822pekbba09nt74ninuihk2 
Returns
The case number of the edited case.

cmd=close

Note: the UI does not let you change any fields on close. The API does. However, ixPersonAssignedTo will always be set to 1 (the CLOSED user).

Parameters
Requires ixBug. Takes and almost all fields that it is possible to edit through the user interface (and a few more).  See parameters for details.  Any fields not specified will remain unedited.
Example
https://kakapo.fogbugz.com/api.asp?cmd=close&ixBug=700token=04t6193822pekbba09nt74ninuihk2
Returns
The case number of the edited case.  

cmd=reopen

Parameters
Requires ixBug and takes ixPersonEditedBy and sEvent.  See parameters for details. Also accepts dt parameter from Site Admins to enable accurate imports with the API.
Example
https://kakapo.fogbugz.com/api.asp?cmd=reopen&ixBug=700&ixPersonEditedBy=10&token=04t6193822pekbba09nt74ninuihk2 
Returns
The case number of the edited case.

List Cases (cmd=listCases)

URL
https://kakapo.fogbugz.com/api.asp?cmd=listCases&cols=ixBug,sTitle,ixPersonAssignedTo&max=2&token=04t9123822q4kbba09nt740inhibk2
fogbugz.py
fb.listCases(cols="ixBug,sTitle,ixPersonAssignedTo",
				max=2)

Parameters

  • sFilter – optional
    • Set this to filter cases
  • cols – optional
    • The columns you want returned about the case
  • max – optional
    • The maximum number of cases to be returned. Defaults to 50,000 if left off or set to 0. The highest this can be set to is 100,000. Anything higher will produce error code 30.

Successful Response

XML
<response>
  <description>
    <![CDATA[ First 2 cases in Kakapo tagged tested ]]>
  </description>
  <cases count="2" totalHits="2">
    <case ixBug="317" operations="edit,assign,resolve,email">
      <ixBug>317</ixBug>
      <sTitle>
        <![CDATA[ User Feedback: 404 Error ]]>
      </sTitle>
      <ixPersonAssignedTo>15</ixPersonAssignedTo>
    </case>
    <case ixBug="363" operations="edit,assign,resolve,email">
      <ixBug>363</ixBug>
      <sTitle>
        <![CDATA[ OAUTH ]]>
      </sTitle>
      <ixPersonAssignedTo>15</ixPersonAssignedTo>
    </case>
  </cases>
</response>

Note that the totalHits attribute can be larger than the number of cases in the response. You can make a second call with a larger max to get all the cases.

Search Cases (cmd=search)

The API differs from the web interface in that, rather than listing cases in one action and viewing specific cases in another, you can return both a list of cases and the exact information you want about them all at the same time using the cols parameter.

Parameters

  • q
    • The query term you are searching for.  Can be a string, a case number, a comma separated list of case numbers without spaces, e.g. 12,25,556 .  This search acts exactly the same way the search box in FogBugz operates, so you can use that to debug.
    • To search for the number 123 and not the case 123, enclose your search in quotes.
    • If q is not present, returns the cases in your current filter.  If the current filter matches a saved or built-in filter, the sFilter is also returned.
  • cols
    • The information you would like returned with each case in the list.  The parameter should be a comma-separated list of column names (e.g., cols=sTitle,sStatus).
    • For Custom Fields and other plugin fields, see this article.
    • ix columns can be empty or 0 if they are not set.  All valid ix columns (ixPersonClosedBy for example) will be > 0 if there is a valid person who closed this case.
    • See below for a full list of column titles.
  • max
    • The maximum number of cases to be returned. Defaults to 50,000 if left off or set to 0. The highest this can be set to is 100,000. Anything higher will produce error code 30.

Example

URL
  https://kakapo.fogbugz.com/api.asp?cmd=search&q=project:inbox%20assignedTo:Elinor&cols=ixProject,ixPersonAssignedTo,sTitle&max=2&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.search(q="project:inbox assignedTo:Elinor", cols="ixProject,ixPersonAssignedTo,sTitle", max="2")

Possible Responses

No cases in your FogBugz account match your query.

No Cases

Your email or password doesn’t match, 2FA might be turned on, etc. This is the equivalent of a failed attempt to log in through the interface.

<response>
  <cases count="0" totalHits="0"/>
</response>
Successful Response
XML
<response>
 <cases count="2" totalHits="11">
  <case ixBug="441" operations="edit,assign,resolve,reply,forward">
  &nbsp<ixProject>2</ixProject>
   <ixPersonAssignedTo>11</ixPersonAssignedTo>
   <sTitle>
    <![CDATA[ Support Request: Site Down ]]>
   </sTitle>
  </case>
  <case ixBug="458" operations="edit,spam,assign,resolve,reply,forward">
   <ixProject>2</ixProject>
   <ixPersonAssignedTo>11</ixPersonAssignedTo>
   <sTitle>
    <![CDATA[ Feature Request: Expanded payment options ]]>
   </sTitle>
  </case>
 </cases>
</response>


Note that the totalHits attribute can be larger than the number of cases in the response. You can make a second call with a larger max to get all the cases.

Column Titles

  • ixBug
    • Case number
  • ixBugParent
    • Parent case number
  • ixBugChildren
    • subcase numbers
  • tags
  • fOpen
    • true if the case is open. false if it is closed
  • sTitle
  • sOriginalTitle
    • Original title for a case opened by an incoming email or a public case submission
  • sLatestTextSummary
    • Short string with the case’s latest comment. Truncated after a limited number of characters
  • ixBugEventLatestText
    • ixBugEvent for latest event with actual text comment
  • ixProject or sProject
    • Project ID/name
  • ixArea or sArea
  • ixGroup
    • Group id (deprecated as of FogBugz 8–will always return 0)
  • ixPersonAssignedTo
    • Person ID of the person assigned to the case
  • sPersonAssignedTo
    • Name of the person assigned to the case
  • sEmailAssignedTo
    • Email address of the person assigned to the case
  • ixPersonOpenedBy
  • ixPersonClosedBy
  • ixPersonResolvedBy
  • ixPersonLastEditedBy
  • ixStatus or sStatus
  • ixBugDuplicates
    • Cases that are closed as duplicates of this one
  • ixBugOriginal
    • The case that this case was a duplicate of
  • ixPriority or sPriority
  • ixFixFor
    • ID of the milestone this case is assigned to
  • sFixFor
    • Name of the milestone this case is assigned to
  • dtFixFor
    • End date of the milestone this case is assigned to
  • sVersion
    • Version field (custom field #1)
  • sComputer
    • Computer field (custom field #2)
  • hrsOrigEst
    • Hours of original estimate (0 if no estimate)
  • hrsCurrEst
    • Hours of current estimate
  • hrsElapsedExtra
    • Additional non-timesheet time on a case
  • hrsElapsed
    • Total elapsed hours — includes all the time from time intervals PLUS hrsElapsedExtra time
  • c
    • Number of occurrences (minus 1) of this bug (increased via BugzScout). To display the actual number of occurrences, add 1 to this number.
  • sCustomerEmail
    • If there is a customer correspondent for this case, this is their email.
  • ixMailbox
    • If this case came in via dispatch, the mailbox it came in on.
  • ixCategory or sCategory
  • dtOpened
  • dtResolved
  • dtClosed
  • ixBugEventLatest
    • The latest Bug Event
  • dtLastUpdated
  • fReplied
    • Has this case been replied to?
  • fForwarded
    • Has this case been forwarded?
  • sTicket
    • ID for customer to view bug (bug number + 8 letters e.g. 4003_XFLFFCS)
  • ixDiscussTopic
    • ID of the discussion topic if case is related
  • dtDue
  • sReleaseNotes
  • ixBugEventLastView
    • The ixBugEventLatest when you last viewed the case
  • dtLastView
    • The date when you last viewed the case
  • ixRelatedBugs
    • Comma-separated list of related case numbers
  • sScoutDescription
    • If this case is a BugzScout case, this ID is the unique identifier
  • sScoutMessage
    • This is the message displayed to users when they submit a case that matches this sScoutDescription
  • fScoutStopReporting
    • Whether we are still recording instances of this crash or not
  • dtLastOccurrence
    • Most recent occurrence of this crash, if this is a BugzScout case
  • fSubscribed
    • True if you are subscribed to this case, false otherwise
  • dblStoryPts
    • Story points set for this case
  • nFixForOrder
    • The position of this case in the Iteration Planner backlog order for the containing milestone
  • events
    • All of the events for a case
  • minievents
    • All of the events for a case, with a subset of the columns included (note: see the example response for the included columns. If you want the complete event records with all columns, use events instead.)
  • ixKanbanColumn2
    • The Kanban column ID for a case (note: The column title is ixKanbanColumn2 although the parameter passed to change the column is kanbanColumn)

Set the Next New Case Number (cmd=adminSetCaseNumber)

This sets the next newly created case to start with this case number. For example, if the current highest case number is 35, and you want the next case number to start at 5000, then you can run this command with the value of 5000. Note that you can only use this command to raise the next value, not lower it. Please note that this cannot be undone.

URL
https://kakapo.fogbugz.com/api.asp?cmd=adminSetCaseNumber&ixBug=1000&token=04t6193822pekbba09nt74ninuihk2 
fogbugz.py
fb.adminSetCaseNumber(ixBug=1000)

Successful Response

XML
</response>

Mark a Case as Viewed (cmd=view)

URL
https://kakapo.fogbugz.com/api.asp?cmd=view&ixBug=282&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.view(ixBug=297)

Parameters

Requires ixBug. Optionally takes ixBugEvent.

Successful Response

XML
</response>

NOTE: Because the new, edit, assign, resolve, reactivate, close, and reopen commands take common parameters and return a common response, you can find those together at the end of this article.

Create a New Case (cmd=new)

URL
https://kakapo.fogbugz.com/api.asp?cmd=new&ixBug=700&ixPersonEditedBy=12&ixProject=10&sTitle=New%20Case%20Created%20via%20API&sEvent=This%20is%20the%20original%20text%20of%20the%20case%20created%20by%20the%20API.&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
resp = fb.new(ixBug=700,
        ixPersonEditedBy=12,
        ixProject=10,
        sTitle="New Case Created via API",
        sEvent="This is the original text of the case created by the api."
        )

curl

JSON Endpoint

curl -X POST -H 'Content-Type: application/json' -d '{"cmd":"new", "token":"e2hesm6udv1h8o9t6gj3b8ul6f2s4s", "sTitle":"Test curl for json", sTags:["testing", "flightless-bird"]}' https://kakapo.fogbugz.com/f/api/0/jsonapi

Edit an Existing Case (cmd=edit)

URL
https://kakapo.fogbugz.com/api.asp?cmd=edit&ixBug=700&ixPersonEditedBy=12&ixPersonAssignedTo=13&sEvent=Marlene%2C%20could%20you%20take%20a%20look%20at%20this%3F&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.edit(ixBug=700,
        ixPersonEditedBy=12,
        ixPersonAssignedTo=13,
        sEvent="This is the first edit to this case."
        )

Reassign an Existing Case (cmd=assign)

URL
https://kakapo.fogbugz.com/api.asp?cmd=assign&ixBug=700&ixPersonEditedBy=12&ixPersonAssignedTo=10&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.assign(ixBug=700, 
        ixPersonAssignedTo=15,
        sEvent="Marlene, could you take a look at this?")

Resolve an Active Case (cmd=resolve)

URL
https://kakapo.fogbugz.com/api.asp?cmd=resolve&ixBug=700&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.resolve(ixBug=700)

Reopening a Closed Case (cmd=reopen)

URL
https://kakapo.fogbugz.com/api.asp?cmd=reopen&ixBug=700&ixPersonEditedBy=10&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.edit(ixBug=700,
        ixPersonEditedBy=10,
        )

Reactivate a Resolved Case (cmd=reactivate)

URL
https://kakapo.fogbugz.com/api.asp?cmd=reactivate&ixBug=700&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.reactivate(ixBug=700)

Reopening a Closed Case (cmd=reopen)

URL
https://kakapo.fogbugz.com/api.asp?cmd=reopen&ixBug=700&ixPersonEditedBy=10&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.edit(ixBug=700,
        ixPersonEditedBy=10,
        )

Close a Case (cmd=close)

URL
https://kakapo.fogbugz.com/api.asp?cmd=close&ixBug=700&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.close(ixBug=700)

Reopen a Closed Case (cmd=reopen)

URL
https://kakapo.fogbugz.com/api.asp?cmd=reopen&ixBug=700&ixPersonEditedBy=10&token=04t6193822pekbba09nt74ninuihk2
fogbugz.py
fb.edit(ixBug=700,
        ixPersonEditedBy=10,
        )

Parameters

In addition to the parameters listed below, each of these commands accepts “ixPersonEditedBy” and “dt” parameters from Site Admins to enable accurate imports with the API. Note that setting ixPersonEditedBy when using the command cmd=new sets who opened the case. For Custom Fields and other plugin fields, see this article.

  • ixBug  – omitted for cmd=new – optional
    • If supplied, the new case is assigned this number. This functionality is provided for importing cases from another system. You must import them in order from lowest to highest case number.
  • ixBugParent
    • Make this case a subcase of another case
  • ixBugEvent – omitted for cmd=new – optional
    • If supplied, and this is not equal to the latest bug event for the case, you will receive error code 9 back to show that you were working with a “stale” view of the case.
  • tags
    • When searching for the tags column via the API, returns a <tags> element with a <tag> for each tag in the case.
  • sTags
    • When editing or creating a case, use the sTags column and submit a comma-delimited list of the tags associated with the case. Existing tags omitted from this list will be removed. If using the JSON endpoint, tags should be passed with case data as an array.
  • sTitle
  • ixProject or sProject
    • If the user associated with the API Token making the call does not have Modify permissions on the project specified, the case will be opened in the first project on which the user does have Modify permission. If the user does not have Modify on any projects, the return will be Error Code 13: Insufficient Permissions.
  • ixArea or sArea
  • ixFixFor or sFixFor – searches project first, then global fixfors
    • (ixFixFor and sFixFor is the API parameter for milestone)
  • ixCategory or sCategory
  • ixPersonAssignedTo or sPersonAssignedTo
  • ixPriority or sPriority
  • ixStatus or sStatus
  • dtDue
  • hrsCurrEst
    • Sets the current estimated time for the case. The first instance of time logged against the case set the most recent current estimate as the original estimate. Future edits with hrsCurrEst will change the current estimate, and the original estimate will remain the same.
  • hrsElapsedExtra
    • This sets additional non-timesheet time on a case. (i.e. if there was an hour long time interval for the case and you set hrsElapsedExtra to 2, then the total hrsElapsed would be 3)
  • dblStoryPts
    • Sets the Story Points for a case.
  • sVersion
  • sComputer
  • sCustomerEmail
    • Case correspondent field
  • ixMailbox
    • If you set sCustomerEmail, you’ll want to set this too… otherwise you won’t be able to reply to this case
  • ixKanbanColumn
    • The id of the Kanban column you’d like to set for a case. See cmd=listKanbanColumns. Will be rejected if selected Kanban column does not belong to the same project as the case. (Note, although the parameter name is ixKanbanColumn, the column name required to retrieve this information through a search is ixKanbanColumn2.)
  • sKanbanColumn
    • The name of the Kanban column you’d like to set for a case. See cmd=listKanbanColumns. Will be rejected if case’s project does not have a matching Kanban column. (Note: sKanbanColumn is not available as a column for search.)
  • sScoutDescription – used only with cmd=new
    • If you set this, and FogBugz finds a case with this sScoutDescription, it will append to that case unless fScoutStopReporting is true for that case, and then it will do nothing.
  • sScoutMessage
    • The message you are supposed to display to users for this case
  • fScoutStopReporting
    • Set this to 1 if you don’t want FogBugz to record any more of these types of cases
  • sEvent
    • Text description of the bug event; or HTML if fRichText is 1
  • fRichText
    • If set to 1, then sEvent is interpreted as HTML
    • Only available for FogBugz On Demand and FogBugz On Site
  • sTicket: The ticket for a case, which can be turned into a public ticket URL
    https://<FogBugz site>.fogbugz.com/default.asp?<sTicket>
  • File1, File2, File3, etc
    • Upload files to the case, no limit to the number of files (constrained only by the max upload limit on the web server).  Use the enctype=”multipart/form-data” form type
  • nFileCount – Required with File1, File2, etc
    • Number of file parameters included in the request. If this is absent, only File1 will upload.

Successful Response

XML
<response>
  <case ixbug="700" operations="edit,assign,resolve,email">
  </case>
</response>

Detailed Case Responses

Case Details

XML
<cases count="1"> -- count is included in the cases attribute
  <case ixBug="123" operations="edit,assign,resolve,reactivate,close,reopen,reply,forward,email,move,spam">
  <ixBug>123</ixBug> -- case number
    <ixBugParent>234</ixBugParent> -- parent case number
    <ixBugChildren>456,876</ixBugChildren> -- subcase numbers
    <tags> -- tags
      <tag><![CDATA[first]]></tag>
      <tag><![CDATA[second]]></tag>
      <tag><![CDATA[third]]></tag>
    </tags>
    <fOpen>true</fOpen> -- true if open, false if closed
    <sTitle>Duck, Duck... but No Goose!</sTitle> -- title
    <sOriginalTitle>Problem finding the goose...</sOriginalTitle> -- original title for a case opened by an incoming email or a public case submission
    <sLatestTextSummary>I searched the docs, but no goose!</sLatestTextSummary> -- short string with case's latest comment
    <ixBugEventLatestText>1151</ixBugEventLatestText> -- ixBugEvent for latest event with actual text comment
    <ixProject>22</ixProject> -- project id
    <sProject>The Farm</sProject> -- project name
    <ixArea>35</ixArea> -- area id
    <sArea>Pond</sArea> -- area name
    <ixGroup>6</ixGroup> -- group id (deprecated as of FogBugz 8--will always return 0)
    <ixPersonAssignedTo>1</ixPersonAssignedTo> -- person case is assigned to (id)
    <sPersonAssignedTo>Old MacDonald</sPersonAssignedTo> -- person case is assigned to (name)
    <sEmailAssignedTo>grandpa@oldmacdonald.com</sEmailAssignedTo> -- email of person case is assigned to
    <ixPersonOpenedBy>2</ixPersonOpenedBy> -- person case was opened by (id)
    <ixPersonResolvedBy>2</ixPersonResolvedBy> -- person case was resolved by (id)
    <ixPersonClosedBy></ixPersonClosedBy> -- person case was closed by (id)
    <ixPersonLastEditedBy>0</ixPersonLastEditedBy> -- person case was last edited by (id)
    <ixStatus>2</ixStatus> -- status (id)
    <ixBugDuplicates>321</ixBugDuplicates> -- cases that are closed as duplicates of this one (id)
    <ixBugOriginal>654</ixBugOriginal> -- the case which this one was a duplicate of (id)
    <sStatus>Geschlossen (Fixed)</sStatus> -- status (name)
    <ixPriority>3</ixPriority> -- priority (id)
    <sPriority>Must Fix</sPriority> -- priority (name)
    <ixFixFor>3</ixFixFor> -- fixfor (id)
    <sFixFor>Test</sFixFor> -- fixfor (name)
    <dtFixFor>2007-05-06T22:47:59Z</dtFixFor> -- date of fixfor (date)
    <sVersion></sVersion> -- version field (custom field #1)
    <sComputer></sComputer> -- computer field (custom field #2)
    <hrsOrigEst>0</hrsOrigEst> -- hours of original estimate (0 if no estimate)
    <hrsCurrEst>0</hrsCurrEst> -- hours of current estimate
    <hrsElapsed>0</hrsElapsed> -- total elapsed hours -- includes all time from time intervals PLUS hrsElapsedExtra time
    <c>0</c> -- number of occurrences (minus 1) of this bug (increased via bugzscout)
      -- to display the actual number of occurrences, add 1 to this number  
    <sCustomerEmail></sCustomerEmail> -- if there is a customer contact for this case, this is their email
    <ixMailbox>0</ixMailbox> -- if this case came in via dispatcho, the mailbox it came in on
    <ixCategory>1</ixCategory> -- category (id)
    <sCategory>Feature</sCategory> -- category (name)
    <dtOpened>2007-05-06T22:47:59Z</dtOpened> -- date case was opened
    <dtResolved>2007-05-06T22:47:59Z</dtResolved> -- date case was resolved
    <dtClosed>2007-05-06T22:47:59Z</dtClosed> -- date case was closed
    <ixBugEventLatest>1151</ixBugEventLatest> -- latest bugevent
    <dtLastUpdated>2007-05-06T22:47:59Z</dtLastUpdated> -- the date when this case was last updated
    <fReplied>false</fReplied> -- has this case been replied to?
    <fForwarded>false</fForwarded> -- has this case been forwarded?
    <sTicket></sTicket> -- id for customer to view bug (bug number + 8 letters e.g. 4003_XFLFFFCS)
    <ixDiscussTopic>0</ixDiscussTopic> -- id of discussion topic if case is related
    <dtDue></dtDue> -- date this case is due (empty if no due date)
    <sReleaseNotes></sReleaseNotes> -- release notes
    <ixBugEventLastView>1151</ixBugEventLastView> -- the ixBugEventLatest when you last viewed this case
    <dtLastView>2007-05-06T22:47:59Z</dtLastView> -- the date when you last viewed this case
    <ixRelatedBugs>345,267,2920</ixRelatedBugs> -- comma separated list of other related case numbers
    <sScoutDescription>Main.cpp:165</sScoutDescription> -- if this case is a Scout case, this ID is the unique identifier
    <sScoutMessage>Please contact us or visit our knowledge base to resolve.</sScoutMessage> -- this is the message
      -- displayed to users when they submit a case that matches this sScoutDescription  
    <fScoutStopReporting>false</fScoutStopReporting> -- whether we are still recording occurrences of this crash or not
    <dtLastOccurrence>2007-05-06T22:47:59Z</dtLastOccurrence> -- most recent occurrence of this crash, if this is a BugzScout case
    <fSubscribed>true</fSubscribed> -- true if you are subscribed to this case, otherwise false
    <dblStoryPts>2</dblStoryPts> -- Story Points set for this case
    <nFixForOrder>10</nFixForOrder> -- The position of this case in the Iteration Planner backlog order for the containing milestone
  </case>
</cases> 

Bug Event Response

XML
<events>
  <event ixBugEvent="174" ixBug="13">
  <ixBugEvent>174</ixBugEvent> -- Identity field in the database for this event
    <evt>4</evt> -- Number for type of event, see event codes
    <sVerb>Assigned to Captain Caveman</sVerb> -- Description of event in English always
    <ixPerson>3</ixPerson> -- Identity field of the person who made this event happen
    <sPerson>Mikey</sPerson> -- Person's full name
    <ixPersonAssignedTo>4</ixPersonAssignedTo> -- Identity field of the person this case is assigned to
    <dt>2007-05-06T22:47:59Z</dt> -- Date event happened (in RFC822 UTC format)
    <s>Up up and away!</s> -- The text of the event (if this is an email or was created in HTML mode via Rich Case Events, this is a plain-text version of the event)
    <sHTML><![CDATA[<strong>Up up and away!</strong>]]></sHTML> -- If this is an event created in HTML mode via Rich Case Events, this contains the raw HTML version of the event
    <fEmail>false</fEmail> -- True if it is an email event
    <bEmail>false</bEmail> -- Deprecated: use fEmail
    <fExternal>false</fExternal> -- True if this case was created via an incoming email, discussion topic, or BugzScout
    <bExternal>false</bExternal> -- Deprecated: use fExternal
    <fHTML>true</fHTML> -- True if the event is an email and the html version has been cached. You should not need to look at this field. Instead use fEmail to determine if the event is an email and sFormat to determine if an edit is html-formatted
    <sFormat>html</sFormat> -- 'html' if the event was created in HTML mode via Rich Case Events
    <sChanges>Project changed from 'Inbox' to 'Cave'.</sChanges> -- Description of changes to the case during this event
    <evtDescription>Captain Caveman von Mikey zugewiesen</evtDescription> -- Description of event in YOUR language (in this case German)
    <rgAttachments><attachment><sFileName>Test Word.doc</sFileName> -- name of the attached file
    <sURL>default.asp?pg=pgDownload&amp;pgType=pgAttachment&amp;ixBugEvent=756&amp;sPart=2&amp;sTicket=&amp;sFileName=Test%20Word.doc</sURL> -- url to hit to get the contents of the attached file (add on token=<yourtoken>)
    </attachment></rgAttachments>-- if the event is an email (fEmail == true) then there are additional fields --
    <sFrom>"JJ Walker" <jj@dynomite.org></sFrom> -- the from header from the message
    <sTo>good@times.org</sTo> -- the to header from the message
    <sCC></sCC> -- the cc header from the message
    <sBCC></sBCC> -- the bcc header from the message (if readable)
    <sReplyTo></sReplyTo> -- the replyto header from the message
    <sSubject></sSubject> -- the subject header from the message
    <sDate>5 Jun 07 21:07:54 GMT</sDate> -- the date header from the message (exactly as it appears usually rfc822 date)
    <sBodyText></sBodyText> -- the body plaintext from the message
    <sBodyHTML></sBodyHTML> -- the message formatted in html
  </event>
</events>

Mini Events Response

XML
<minievents>
  <event ixBugEvent="174" ixBug="13">
  <ixBugEvent>174</ixBugEvent> -- Identity field in the database for this event
    <evt>4</evt> -- Number for type of event, see event codes
    <sVerb>Assigned to Captain Caveman</sVerb> -- Description of event in English always
    <ixPerson>3</ixPerson> -- Identity field of the person who made this event happen
    <sPerson>Mikey</sPerson> -- Person's full name
    <ixPersonAssignedTo>4</ixPersonAssignedTo> -- Identity field of the person this case is assigned to
    <dt>2007-05-06T22:47:59Z</dt> -- Date event happened (in RFC822 UTC format)
    <fEmail>false</fEmail> -- True if it is an email event
    <fHTML>false</fHTML> -- True if the event is an email and the html version has been cached. You should not need to look at this field. Instead use fEmail to determine if the event is an email and sFormat to determine if an edit is html-formatted
    <sFormat></sFormat> -- 'html' if the event was created in HTML mode via Rich Case Events
    <fExternal>false</fExternal> -- True if this case was created via an incoming email, discussion topic, or BugzScout
    <sChanges>Project changed from 'Inbox' to 'Cave'.</sChanges> -- Description of changes to the case during this event
    <evtDescription>Captain Caveman von Mikey zugewiesen</evtDescription> -- Description of event in YOUR language (in this case German)
      -- if the event is an email (fEmail == true) then there are additional fields --
    <sFrom>"JJ Walker" <jj@dynomite.org></sFrom> -- the from header from the message
    <sTo>good@times.org</sTo> -- the to header from the message
    <sCC></sCC> -- the cc header from the message
    <sBCC></sBCC> -- the bcc header from the message (if readable)
    <sReplyTo></sReplyTo> -- the replyto header from the message
    <sSubject></sSubject> -- the subject header from the message
    <sDate>5 Jun 07 21:07:54 GMT</sDate> -- the date header from the message (exactly as it appears usually rfc822 date)
  </event>
</minievents>